Page History

...

The Condition element has two child tags both of which are mandatory:

• The name tag defines the name of the condition by which it can be referred to later
• The filter tag defines the condition itself. The syntax is same as in the Query Builder so the condition can be created in the Query Builder and then copied to the XML.

Actions

The action element is used to define the action itself.

<action>
  <name>Resolve As</name>
  <condition>Open</condition> <!-- <filter>status in (UNCONFIRMED NEW ASSIGNED REOPENED)</filter> -->
    <set>
      <!-- action script -->
    </set>
</action>

Mandatory action propertiesIt consists of thee mandatory sub-elements:

• name The displayable name tag, which defines the name of the action . This text is used to show action on shown in the UI components (such as menusWorkflow drop-down list).
• Action applicability . Applicability defines when the action can be performed against the bug. If the bug passes action applicability condition the action is applicable otherwise it is not. It can be defined by referring to defined Condition\ with condition tag or by specify special statement with filter tag. The content of filter tag has same syntax as conditions\.set tag that defines the action script, what happens to the bug when condition, which defines which conditions an issue 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 run when the action is applied. The script may define fixed changes or contain questions to usercontain 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 status is changed).

Optionally an action may provide contain the windowId child tag. The content of the tag defines identifier to store , 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. This tag can be used to reuse one configuration for several actions

Below is the explanation of the Action script syntax.

Action script

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

<attribute>
  <name>status</name>
  <value>RESOLVED</value>
</attribute>

Action script defines zero or more modifications of a bug (action that defines no modifications has no sense but seems legal). Each modification defines what field of the bug is altered and how it should be alteredBelow is the description of tags used to define the fields change.

value: Change field to predefined value

...