“If debugging is the process of removing bugs, then programming must be the process of putting them in.” – Edsger Dijkstra
This is the Bug Tracking System for the Flyspray project. This is not a demo! Before opening a new task, please read the guidelines!
Do not issue bugs reports against versions earlier than 0.9.9.6
Security problem? Check the security section.
FS#1222 - Wanted - a workflow engine / Role-based State Transition Rules Engine
Opened by Srivathsan M (m.srivathsan) - Sunday, 25 March 2007, 17:16 GMT+2
|
DetailsI have been working with Eventum (http://www.mysql.org/downloads/other/eventum/) for quite sometime now and in Contrast, I like Flyspray for its simplicity and practicality. But one thing I badly miss (and something that Eventum scores high) is a Workflow Engine. If not a sophisticated W.E., I (as an Admin / Manager) should be able define Role-based State Transition Rules of the Tasks reported in a particular Project. For example, I should be able to implement the following Scenario: 1. For a "Developer", the subsequent tasks from various states. Likewise for other roles 2. "Developer" should not be able close out the Bug Reports. He / She can only flag them as implemented. The "Reporter" of the Bug(s) or the "Manager" alone should be able to close out issues : : - it will go on like that ;-) This Feature, in my opinion, is very crucial for Corporate Organizations to give a serious consideration to Flyspray. |
Isn’t what you mentioned already possible using the permission system? If you give examples for a new feature, they should show what is *not* possible currently.
Flyspray will probably never be suitable for “big corporations” and that is the expected behaviuor. ;) that kind of users needs Bugzilla or something much more better designed like Jira, we dont target them, it is not our goal.
In any case, we will love to hear about what is missing (in detail) and how you think the missing features should be implemented.
Sorry for the late reply (for the comments of Florian and Cristian).
The Permission System of Flyspray is really better than that of Eventum’s. But what I could not do is to limit / control the Task Statuses available for a particular task, based on the User Role of the currently logged on User, Task Type and the current Task Status. I would prefer that this is achieved through something that is very similar to the Permission System - or even an extension to it.
For example, in our company, we have a workflow by which the Reporter (one who submits bugs) re-checks the Tasks and flag them as “Verified OK” or “Verify FAILED” after which the Project Manager can appropriately close them out (as either “DONE” or “FAILED”). The Reporter should not be able to change to any other Status while he can just view the Status being changed by the Developers.
If the above could be achieved through the current System, I would like to know about it.
No, it cannot. Before we can ever consider implementing it though, we have to find a way how to easlily implement this, without any complexity. Maybe you can give a few more examples what might be needed?
“Group”, “Task type” - to manage workflow
St1, St2, St3 * Status1 chk chk chk * Status2 chk chk chk * Status3 chk chk chkIt’s a a table with NxN status collumns where chk is check button and defines the horizontally status transition for selected
is how the issue is implemented in the redMine project management system http://www.redmine.org/ :)
sorry for the formatting... :(
I figure I would chime in here.
Our site (http://www.mp3car.com) produces the software 'StreetDeck'. This is a software front end for use with CarPCs to make using CarPCs in the automotive environment easier. Currently this is the bug tracking system I've hacked together using mods with vBulletin: http://www.mp3car.com/vbulletin/streetdeck-bug-reports/
It works ok but it's difficult to keep track of it all and I'm running into issues with the forms and user groups.
By nature, I don't want the users to have the right to assign severity because they all think their issue is the top issue out there. The developers and staff need to be able to assign severity based on work flow.
Such a thing is already possible. In 1.0 you can "force default" of a field, that will only allow users who can modify all tasks to change it.
Just so I can be sure I understand this:
If you select the check box in the 'force default' column, then no matter what the field is, it will only allow users who can modify all tasks to select other items in that list?
Right.
Sorry about the double post. didn't realize I still had it in my browser.