Tech review

Style guide



On this page



Use case

Keeping parent issues and sub-tasks is often a real word use case, as described in this use case. The following automation rule keeps not a field value in sync but updates the sub-tasks' status depending on the parent issue's status: When the parent issue is rejected, all sub-tasks are transitioned to accordingly.



Automated action

Transition Issue

Use case descriptionWhen an issue is transitioned to 'Draft' status, the issue will be assigned to the last assignee from the project role 'Developers'
Complexity




Issue Transitioned Event



Add a Trigger → Issue Transitioned Event.

No further configuration needed. The automation rule is triggered every time an issue is being transitioned.



Boolean Condition

Add a Condition → Boolean Condition


Expression*

Use the following Parser Expression:

%{trigger.issue.status} = "Rejected"



Boolean expressions are logical constructions that return true or false .
In this use case, the expression will only return true if the status of the issue triggering the rule is .




Issue Selector

Next to the Boolean Condition click on Add →  Selector → Issue Selector


Target Issue(s)*

Choose Sub-tasks


Transition Issue

Next to the Issue Selector click on Add → Action → Transition Issue


Mode*

Choose Execute transition


Choose your project


Choose Close issue






Screencast

This is how the configuration above should look on your screen

Related examples