Tech review

Style guide



On this page



Automated action

Transition issue

Use case description

When an issue is being rejected, all sub-tasks will be transitioned to the  status as well - automatically.

Complexity




Use case

Keeping parent issues and sub-tasks in sync, as described in this use case, is a lot of manual work. This automation rule will update the status of all sub-tasks based on the parent status: When the parent issue is rejected, all sub-tasks are also being rejected.



When to use this automation rule and when to use a workflow post function?

This use case is very useful, if there are several software projects with different workflows where all related issues have to be closed on releasing a new version. Configuring just one automation rule might then be the easier way to go. But if this scenario is only necessary for one workflow, the Transition Issues post function would make more sense. In this case you might want to check out our corresponding post function use case.




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 action

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


Mode*

Choose Execute transition


Choose your workflow


Choose Close issue






Screencast

This is how the configuration above should look on your screen

Related use cases