Deskzilla application allows users to customize the bugs workflow by defining a set of actions which can be applied to a bug or a number of bugs. The actions (for example, Resolve As, Reassign, Close, etc) are defined in the XML file and can be accessed through the Workflow drop-down menu on the Bugs Toolbar.
Below is the explanation of the XML file structure and tags used to define new workflow actions, which will allow you to create new actions and modify the existing ones.
Default Workflow
TBD
By default, workflow actions are pre-configured for the standard Bugzilla workflow. Starting with Bugzilla version 3.2, Bugzilla administrator can customize statuses and workflow in Bugzilla, and so you might need to change the definition of the workflow in workflow.xml accordingly.
| Tip |
|---|
Even if you don't change workflow.xml, you still will be able to change status for a bug using Edit Bug dialog. However, workflow actions are useful to make bulk changes and to change several fields at once. |
Actions
The action tag is used to define the action and its preconditions.
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
<action> <name>Resolve As</name> <condition>Open</condition> <!-- Or, instead of condition tag: <filter>status in (UNCONFIRMED NEW ASSIGNED REOPENED)</filter> --> <set> <!-- action script --> </set> </action> |
It consists of three mandatory sub-elements:
...
| Tip |
|---|
The Workflow.xml file uses the same syntax as the Query Builder for conditions definition, so the statements can be first created in the Query Builder and then copied to the XML file. To do that, open Query Builder, create the query with the required filter in the Query Builder, then right-click on the created query in the navigation pane condition in Filter: section in the Query Builder and select Copy. Then paste it in the XML filethe text from the clipboard into the <filter> tag. |
Action Script
Action script is provided in the set tags and defines a number of changes that are made to the bug as a result of the action (the action that defines no changes does not make sense, but is valid). Each script element defines which field of the bug is altered and how.
...
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
<attribute> <name>resolution</name> <askReference>$(bz.field.Resolution!mnemonic=r):</askReference> <exclude>N/A</exclude> <exclude>DUPLICATE</exclude> </attribute> |
The content of askReference specifies the label text.
...
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
<attribute> <name>duplicate_of</name> <askString>$(bz.field.DuplicateOf!mnemonic=d):</askString> </attribute> |