Page History
...
- create a new rule and define the "When" (i.e. when it to should be triggered) , to be "Issue linked". Since Xray, by default, uses the issue link type "Tests" to establish the coverage relation between a Test and the requirement, we can take advantage of that to trigger the rule whenever such issue link is created.
- create a condition to ensure that the rule only runs for Test issues
- use a an "Edit issue" action to set the fields on the Test , based on the field fields of the linked requirement/Story (i.e., the destination issue of the issue linking event). In this example, we'll copy the values of Urgency and Probability custom fields.
...
- whenever a Test is created from the requirement/Story issue screen
- whenever a Test has been initially created and linked later on linked to the requirement
Reopen/
...
transitionTests linked
...
to a requirement
...
whenever
...
the requirement is transitioned or
...
changed
Whenever you change the specification of a requirement/story, you most probably will need to review the Tests that you have already specified.
The following rule tries to make perform a transition on of all Tests linked Tests to a requirement.
Automation configuration
...
- create a new rule and define the "When" (i.e. when it to should be triggered) , to be "Field value changechanged"
- Note: we could also define the trigger to be based on the transition of the requirement issue to a certain workflow status; in that case we would define it, for example, as shown aheadbelow.
- create a condition to ensure that the rule only runs for Story and Epic issues; adjust these to include all the "requirement" issue types (i.e., the ones that you can cover with Tests)
- create a "branch rule / related issues" to obtain related Tests using JQL and the
requirementTests()JQL function and run one, or more, action(s) on them - under the "For JQL" block, create a action "Transition the issue to" in order to reopen the related Test issues
...