...
To define actions a set of tags is used. See below for detailed explanation.
Conditions
...
<condition>
<name>Open</name>
<filter>status in (UNCONFIRMED NEW ASSIGNED REOPENED)</filter>
</condition>
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.
| Tip |
|---|
The Workflow.xml file uses the same syntax as the Query Builder for conditions definition, so the statements can be created in the Query Builder and then copied to the XML file. |
Actions
The action element is used to define the action itselfand its preconditions.
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
<action>
<name>Resolve As</name>
<condition>Open</condition> <!-- <filter>status in (UNCONFIRMED NEW ASSIGNED REOPENED)</filter> -->
<set>
<!-- action script -->
</set>
</action>
|
...
Below is the explanation of the Action script syntax.
Conditions
| Anchor | ||||
|---|---|---|---|---|
|
Issues 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.
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
<condition>
<name>Open</name>
<filter>status in (UNCONFIRMED NEW ASSIGNED REOPENED)</filter>
</condition>
|
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.
| Tip |
|---|
The Workflow.xml file uses the same syntax as the Query Builder for conditions definition, so the statements can be created in the Query Builder and then copied to the XML file. |
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.
...
Below is the description of tags used to define the fields change.
value: Change field to predefined value
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
<attribute> <name>status</name> <value>RESOLVED</value> </attribute>> |
This tag is now applicable only to enumeration fields (such as status or assignee). The content contains textual presentation of desire value. This modification is shown to user on action window but can not be modified.
...