Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,467,410
Community Members
 
Community Events
177
Community Groups

Transition Initiative to In Progress when Epic starts

I am using Advanced Roadmaps to create initiatives and set the Parent Link for Epics. I want to transition the Initiative to In Progress when at least one Epic starts. I have tried many different things but they have all failed to work. I would like to do this without purchasing another add-on as I believe this should be native functionality.

My structure is like this: Initiative -> Epic -> All other Standard Issue Types -> All Sub-Task issue types. Epics will be set with a 'Parent Link' to the initiative.

Is there a way for me to do this using Automation?

4 answers

1 accepted

11 votes
Answer accepted

I think I figured out how to get this working. You can use a new Variable or just set the smart value directly in the JQL.

  1. Set your Branch rule to use JQL -> use this query: issuetype = Initiative AND issuekey = {{issue.Parent Link.data.key}}
  2. Create a new Variable called {{parentLink}} -> set Smart value with {{issue.Parent Link.data.key}}. Next, set your Branch rule to use JQL -> use this query: issuetype = Initiative AND issuekey = {{parentLink}}

Keep in mind if your Parent Link issue type is not 'Initiative' then just replace Initiative with whatever you're using. I hope this helps someone else.

initiative to in progress.png

Deleted user Jul 14, 2021

spent 4 hours on this problem until I found your post! many thanks!

Like Michael likes this

Thankyou Michael, been struggling with this one for awhile. Great answer, easy to follow.

Like Michael likes this

How would you test for Initiative existence first? The rules throws an error when one is not linked.

You can try checking if the {{parentLink}} is not empty before proceeding else log something to the audit log--see screenshot below. I have not tested this so it might not work but give it a shot.

Screenshot 2021-10-26 091333.png

Like # people like this

How I create a smart variable? I am not seeing that on JIRA DC automation.

Also would this be possible if Initiative are on one project and Epics are on a different project. Our setup has all of our Initiatives in a single jira project  and Epics are on different team projects.

Like # people like this

@Davor Fisher when you add a new action, do you see this option

Screenshot 2021-11-19 151254.png

I set up a global rule so I don't think it cares which project the Initiative is in as long as it is the parent issue of the Epic.

Michael,

I do not. It must be just available on the cloud which is unfortunate as teams would love to have this functionality. 

 

Davor

I did some looking around and you're right, it is not in server yet. You can try using option 1 I mentioned above. Here it is again for reference:

  1. Set your Branch rule to use JQL -> use this query: issuetype = Initiative AND issuekey = {{issue.Parent Link.data.key}}
Like Quentin Laudrain likes this

Thanks for this post.  Unfortunately, {{issue.Parent Link.data.key}} does not contain a value, at least in DC version 8.13.10.

Any pointers from the Atlassian team on how to solve this for us poor on premise users?

Hah.  Got it working with just {{issue.Parent Link}}.

Like # people like this

For Data_Center

there is not option to create variable, and for some reason rule branch[Parent] didn't work nor other options.

 

however after many hours I was able to make it work 

JQL > issue in parentIssuesOf("{{issue.key}}")

Related Issues Condition > issue IN ChildIssuesOf("{{issue.key}}") and issuetype=epic

Matches >issue IN ChildIssuesOf("{{issue.key}}") and issuetype=epic and status = Done

 

what this rule does it will change the status the initiative Epics' were done, 

obviously you can modify it as per your need 

AutomationRulePNG.PNG

 

To save your time double check the status transitions,

I had an issue whatever I was doing to the rules nothing seems to be working

eventually I've found out it was due The Transitions on the workflow 

therefore it was not changing the status from To Do > Done once I added the missing transitions the rules start working.

 

Hi @Michael

In addition to the use case above: is there a way to set the status of the initiative to 'Done' when all the childs (epics) have the status 'Done'? I can't figure it out with the existing options you can choose from in the 'branche rule', sub field: 'Type of related issues'. This is what I've tried so far.

Any idea? Many thanks!2021-12-09 16_26_02-Clipboard.png

I think I figured it out. The following options should automatically set the status of the initiative to DONE when all the child issues (epics) were on status DONE.

2021-12-09 16_26_02-Clipboard.png

Like # people like this

@Sander Voskuilen thank you, but what is your value at {{parentLink}}? {{issue.Parent Link.data.key}} and {{issue.Parent Link}} isn't working for me. 

Hi @Noah Dellenbusch ,

Have you created the variable with the correct settings? Shown below how my settings are set.

Screenshot 2022-07-10 at 21.39.47.png

After that, it should work! Or are you Server? Then you do not have the option to create a variable.

Like Noah Dellenbusch likes this

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events