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,361,196
Community Members
 
Community Events
168
Community Groups

Automation for Advanced Roadmap layers

Edited

I need help to know how I can automate changes in Advanced Roadmap based on changes in its linked projects. I my case, I want to change the status of 4 layers above a custom field from "Draft/not initiated" to "In Progress" when an epic becomes in progress.

 

As shown in the picture below, I already have an automation rule which rolls up the status from an Issue up to an Epic; and, From Epic to Advanced Roadmap. The next step is to update the fields from the “Advanced Roadmap Instance” based on values from the projects that are linked to itAdvanced RoadMap Automation.jpg

2 answers

1 accepted

2 votes
Answer accepted

Hi @Moe_Madjdi 

If I understand your request correctly, the key here is, that you need to use JQL in the automation to find the correct Parent issue to transition.  The key here is the JQL function:

issuekey in parentIssuesOf("ABC-123")

You can find additional information in a similar request:

https://community.atlassian.com/t5/Advanced-Roadmaps-questions/JQL-to-get-details-of-linked-parent-initiatives/qaq-p/1295379

In a Jira Automation rule, you need to create a branch based on JQL. The Automation could look similar to the picture below:
Automation_PortfolioParent.png

In your case, the JQL needs to be more specific to also search for the specific issue type (AND issuetype = XYZ). Please test the JQL before using it in Automation.

I hope that helps with your request.

Hi @Mathias,

 

Thanks for the post. The challenge is that we can't update the status of a parent issue which its parent is in another Jira project. This is the case in the screen shot that I sent.

 

However, for issue types that in the same Jira project, I used a simpler workflow that worked as below.

 

Jira Automation.png

Happy to hear that you found a solution @Moe_Madjdi ! 

Just want to point out, that the branch you used (Epic (parent)) is only transitioning Epics not the parent Objects above the Epic.

Like Moe_Madjdi likes this

I see. Is there a way to update the parent object above the Epic? I don't think so.

You should be able to update the parent issue using the Automation I provided on 11-Aug. This requires ScriptRunner installed in your environment.

If you have that, the JQL I provided should work and return the current parent of the epic

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS

Atlassian Community Events