Child pages
  • How to Customize the Bugs Workflow

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Deskzilla application allows users to customize the issues bugs workflow by defining a set of actions which can be applied to an issue a bug or a number of issuesbugs.

The actions (such as, for example, Resolve As, Reassign, Close, etc) are defined in the XML file and can be accessed through the Workflow combo box on the Issue Bugs Toolbar. Below is the explanation of the XML file structure, which will allow you to create new actions and modify the existing ones.

...

  • The name tag, which defines the name of the action shown in the UI components (such as Workflow combo box).
  • Action applicability condition, which defines which conditions an issue a bug must meet to be eligible for the action. Action applicability can be defined either by referring to the condition defined earlier or by specifying a filter statement using the filter tag and the same syntax as is used for the condition definition.
  • The set tag, which defines the action script which runs when the action is applied. The script may contain both defined actions (for example, change the status value to Closed for the Close action) and actions, which require user input (for example, get the user comment when the issue bug status is changed).

Optionally an action may contain the windowId child tag, which defines the window identifier used to refer to the visual properties of the action window (such as size, position, etc). This identifier can be used to apply one window configuration for several actions. If not specified the action name is used to generate the identifier.

...

Anchor
conditions
conditions
Issues
Bugs must meet specific conditions to be eligible for the action. These conditions are defined outside the action tags using the condition tag and then used in the action element.

...

Action script is provided in the set tags and defines a number of changes that are made to the issue 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 issue bug is altered and how.

Below is the description of tags used to define the fields changes.

...

This tag can only be used to add comments to an issue a bug and should be used as shown in the example.
Content of askAddTextElement defines the text box label. Content of checkbox defines the label shown next to the "private comment" checkbox, which defines if the comment is visible to other users. Content of both tags can be filled with any text.

...