I am trying to build automation such that as soon as the "Roadmap Item" is set to 'In progress', the rule should change the status of the "Initiative" to 'In Progress'. This is an example query I am using to trigger the automation rule -
issue in portfolioChildIssuesOf(IA-123) and (statusCategory = "In Progress" or statusCategory = Done) and "Roadmap Item Health[Dropdown]" in (Green, Red, Yellow, Blue) ORDER BY key asc
The output of the above query will give me the Roadmap Item which is in progress or done and the Roadmap Item health status is either Green or Red or Yellow or Blue. I am unable to find ways to update the Initiative of the Roadmap Item coming from the above query. I tried using the "For Parent" branching but looks like it does not work when we try to make use of Advanced Roadmap.
Is there any way I can change the trigger issue (in this case Roadmap Item) to "Initiative" on fly using JIRA Automation? If it can be done then I can simply be able to use the "For" branch to transition the "Initiative" to 'In Progress'.
Thanks in advance.
Hi @Akhil Mishra,
Your plans are structured through an issue hierarchy. That means that you only have to change the status of your initiative to In Progress as soon as its first child issue (which will usually be an Epic) transitions to In Progress.
That is pretty simple to automate like this:
In a similar fashion, you can automate the status transitions of your Epics as soon as a child issue transitions to In Progress.
Hope this helps!
Thanks @Walter Buggenhout . Unfortunately, the 'For Parent' branching is not working since I am working with Roadmap Item and Initiative of the Advance Roadmap. Looks like JIRA doesn't recognize the 'Initiative' as Parent for the 'Roadmap Item' and so when I use 'For Parent' it simply doesn't do anything.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Akhil Mishra,
I can imagine that. Just look at the hierarchy configuration of your advanced roadmap setup to see how items in your plan are linked to the higher levels of your hierarchy. Children can only update their own parent in the way I described. And then again, those can update their parent. And so on.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
For my query above, got to know that there are already a couple of tickets placed with the Atlassian team on building Automation in JIRA for Portfolio in Advanced Roadmap -
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.