Get started

Use case library

JWT expression editor

JWT expression parser functions

JWT workflow functions

JWT remote actions

JWT automation rules

JWT calculated fields

JWT calendars

JWT properties

JWT JQL functions

Cloud migration hub

Additional product info

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 12 Next »

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 REJECTED accordingly.


 Issue Transitioned Event

Create a new rule and name it appropriately.

Providing a description will help you to identify what the rule does but this step is optional.


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 REJECT.

 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


Error rendering macro 'excerpt-include'

No link could be created for 'DECADIS:Automation Use Case - Activate Rule Step'.

Screencast

This is how the configuration above should look on your screen



Related examples

Use caseTypeFunctionUse case descriptionComplexity
Add comment after seven days in the same status    
Add components of the epic to the current issue    
Add links to the issues in a ScriptRunner Issue Picker field    
Add sub-tasks to an automatically created issue    
Add sub-tasks to an issue on creation    
Assign an issue to the last assignee on a transition    
Assign issues to your team during a transition    
Automatically assign issues to your team    
Automatically close parent when all sub-tasks are done    
Automatically close sub-tasks when parent is completed    
Bulk clear the issue resolution    
Bulk edit the issue resolution    
Close epic when stories are done    
Close stories when epic is done    
Copy excerpted value from new comments    
Copy the parent issue comments to its sub-tasks    
Create issue link when issue is created    
Create sub-tasks depending on selected values in a custom field    
Delete the attachments of an issue 30 days after closing it    
Inherit value from parent in Advanced Roadmaps hierarchy    
Keep calculated custom field in sync    
Keep the priority of parents and sub-tasks in sync    
Keep the status of parents and sub-tasks in sync    
Manually create test issues    
Manually delete test issues    
Notify about date of last comment for high priority issues    
Notify assignees when components are merged    
Notify for high priority issue    
Notify the assignee one week before the due date    
Notify the project lead on priority changes    

If you still have questions, feel free to refer to our support team.