Versions Compared

Old Version 1

changes.mady.by.user Christian Czaia

Saved on

compared with

New Version 2

changes.mady.by.user Iheb Kharab

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Page properties
hiddentrue


Tech review

Status
colourGreen
titledone

Style guide

Status
colourGreen
titledone

Status
titletodo
Status
colourYellow
titleReady for review
Status
colourGreen
titledone
Status
colourRed
titleflagged



Panel

On this page

Table of Contents
exclude(On this page|Use case).*
stylecircle
typeflat
separatorpipe


Page properties
hiddentrue


Automated action

Transition issue

Use case description

When an issue is being rejected, all sub-tasks will be transitioned to the 

Status
colourGreen
titlerejected
status as well - automatically.

Complexity

Status
colourGreen
titleBeginner




UI Text Box
sizemedium
typeinfo

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.


UI Expand
titleShould I use an automation rule or a workflow post function?


Tip
sizemedium
typetip

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.




UI Steps

Issue transitioned event

UI Step

Excerpt Include
DECADIS:Automation Use Case - Create Rule Step
DECADIS:Automation Use Case - Create Rule Step
nopaneltrue


UI Step

Add a Trigger → Issue transitioned event

UI Text Box
typeinfo

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



Boolean condition

UI Step

Add a Condition → Boolean Condition


UI Step

Expression*

Use the following Parser Expression:

Code Block
linenumberstrue
%{trigger.issue.status} = "Rejected"


Expand
titlemore info...


UI Text Box
iconfalse
typeinfo

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

Status
colourGreen
titleRejected
.




Issue selector

UI Step

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


UI Step

Target Issue(s)*

Choose Sub-tasks


Transition issue action

UI Step

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

UI Steps


UI Step

Mode*

Choose Execute transition


UI Step

Choose your workflow


UI Step

Choose Close issue




UI Step

Excerpt Include
DECADIS:Automation Use Case - Enable Rule
DECADIS:Automation Use Case - Enable Rule
nopaneltrue



Screencast

This is how the configuration above should look on your screen

Multimedia
nametransition_sub-tasks_when_parent_issue_is_rejected.mp4
width700

Related use cases

Page properties report
firstcolumnUse case
headingsAutomated action, Use case description, Complexity
sortByTitle
cqllabel = "use-case-auto" and label = "transition-issue" and space = "JWTSDC"

Excerpt Include
DECADIS:Contact support
DECADIS:Contact support
nopaneltrue

...