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?
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.
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.
spent 4 hours on this problem until I found your post! many thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thankyou Michael, been struggling with this one for awhile. Great answer, easy to follow.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
How would you test for Initiative existence first? The rules throws an error when one is not linked.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
How I create a smart variable? I am not seeing that on JIRA DC automation.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Davor Fisher when you add a new action, do you see this option
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Michael,
I do not. It must be just available on the cloud which is unfortunate as teams would love to have this functionality.
Davor
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hah. Got it working with just {{issue.Parent Link}}.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I needed this today. Thank you Michael.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hi,
DC ver 9.4 it also worked with Branch by linked issues - type "child of"
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Noah Dellenbusch ,
Have you created the variable with the correct settings? Shown below how my settings are set.
After that, it should work! Or are you Server? Then you do not have the option to create a variable.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I've tried this rule creation but it is not working since the JQL is not formed precisely, could you please send the complete screenshots of this automation rule if possible, that will significantly help full for me.
Thank you in Advance!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.