Question

I want to change the Bugzilla workflow so that a user won t be able to close a bug unless the bug has gone through some phases (e.g. ASSIGNED, IN_PROGRESS, etc).

How do I change Bugzilla in order to create my own work flow?

Answer 1

Have you tried changing the workflow from within bugzilla itself?

(Edit: updated URL for 5.0)

Answer 2

If your primary concern is permissions, you ll want to check out check_can_change_field in Bugzilla/Bug.pm.

Answer 3

There s only so much customization you can do in editworkflow.cgi, because RESOLVED much be reachable from any other status (because when it is marked as a duplicate, for instance, it becomes RESOLVED). The workflow itself doesn t consider the history of the bug.

If you really wanted to enforce this sort of business logic, you should start diving into process_bug.cgi. If someone want to set the status to FOO but it needs to have been in status BAR before, you could check the bug s history in bugs_activity.

But that s a lot of work, and you re likely to have special cases, more rules, more special cases, etc.

I think you would be better off identifying bugs that didn t go through the proper workflow after the fact. When you identify such a bug, you would reopen them or put them into whatever status.

You would do this by examining bugs_activity to see what values of bug_status have been added/removed.

Answer 4

You need to do it in two steps:

Go to editvalues.cgi?field=bug_status and add/delete/rename the names of the different status.
Go to the editworkflow.cgi and customize the matrix.

Answer 5

Create first a status. Type "closed" to Status type (Administration/Field values/Status (This value will not be used (for example the name "Do not use"))
Go to Admininistration/Parameters/Bug change policies. Choose your new status
Go to Edit workflow (Admininistration/Bug Status Workflow). You can now uncheck RESOLVED

It is a way of doing

友情链接