nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to trigger status change automatically for parent based on its children's statuses?

Saurabh Zunke

We have a two level Issue Type hierarchy for our use case.

Parent --> Child --> Grandchild
(these are set up using Portfolio for JIRA so are separate Issue Types and not Sub-Tasks)

e.g.

A (Parent) --> B, C (Child)

B (Child) --> D, E (Grandchild)

C (Child) --> F, G (Grandchild)

We want to cascade status updates from the Grandchild level all the way up to Parent level. i.e. If one or more grandchild moves from NEW to IN-PROGRESS, the parent automatically moves from NEW to IN-PROGRESS - applicable across all hierarchies

Considering this example, details are as follows:

a) When D or E moves from NEW to IN-PROGRESS, its Parent B will move from NEW to IN-PROGRESS and furthermore its own parent A will move from NEW to IN-PROGRESS

b) When D & E both move from IN-PROGRESS to COMPLETE, its Parent B will move from IN-PROGRESS to COMPLETE

c) When all D, E, F & G are COMPLETE, and their Parents B & C will be COMPLETE and furthermore, the Grandparent A will move from IN-PROGRESS to COMPLETE

What is the best way of implementing this functionality?

We are considering Automation for JIRA plugin and also running a custom script using Scriptrunner

Thanks in advance for all your responses!

Accepted answers

Scott Harwood

Hi Saurabh,

The answer is it depends on what issue types your using. If your using standard issue types than you can sync the parent by using a related issues branch with the JQL:

"Parent Link" = {{issue.key}}

For example:

Screen Shot 2018-08-07 at 2.32.44 pm.png Then to ensure the transition continues to bubble all the way up the hierarchy you will also need to ensure this checkbox is checked on the rule details:

If your hierarchy contains the "epic" issue type, the parent link is maintained via the "epic link" field instead of Parent link. So, in that case, you need to alter the rule to use an if/else block that checks the issue type and if it matches epic than do the branching on "epic" rather than JQL. Let me know if this is the case an I can go into more detail, I don't want to over complicate this solution.

Let me know if that works for you.

Cheers,

Scott

All comments

Scott Harwood

Hi Saurabh,

The answer is it depends on what issue types your using. If your using standard issue types than you can sync the parent by using a related issues branch with the JQL:

"Parent Link" = {{issue.key}}

For example:

Screen Shot 2018-08-07 at 2.32.44 pm.png Then to ensure the transition continues to bubble all the way up the hierarchy you will also need to ensure this checkbox is checked on the rule details:

Let me know if that works for you.

Cheers,

Scott

Saurabh Zunke

Thanks for the reply Scott.
We were able to use the plugin to implement our requirements.

Rasmus Vedel_hm073a

Do you know any way I can do "the opposite":

I want to have all the children have their individual status UNTIL I click done to the parent-issue, then I want all children to be done as well.

Do you know how to do that?

Rasmus

Nachiket Bal

@Scott Harwood

I tried using the solution you mentioned in the above thread, the behaviour i am seeing is exactly opposite.

When the Children change status for Eg: All go to complete the Parent does not move from In-Progress to Complete, but when the Parent status is changed from in-progress to complete all the children move to complete. What am i doing wrong?

Thanks

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

scriptrunner

jira

addon-com.codebarrel.addons.automation

jira-server

advanced-roadmaps