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,551,871
Community Members
 
Community Events
184
Community Groups

Creating Parent links in automation rules (advanced Roadmaps / Premium)

I guess I'm running against an issue of poor integration of advanced roadmaps into Jira.

I'm using a issue type in hierarchy, one level above the Epic, in advance Roadmaps 

Under some conditions I want to make automatically an epic and give that Epic the issue from Advanced roadmap as the Parent link (not to confuse with linked issues in JIRA!!).

Unfortunately I can not find the field "parent link" in the list when I create the automation rule.  

Am I correct that this is missing? If not, how can I fill the "parent link" field. If correct, is this issue already on the backlog from Atlassian to solve, as it really restricts the added value of Advanced Roadmaps? (more in general, the mix-up between link fields of JIRA and Parent link field for Adv Roadmaps works very confusing.

1 answer

1 accepted

0 votes
Answer accepted
John Funk
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Mar 20, 2023

Hi Jeroen,

You might try using the More options when creating the issue and add something like this:

{

  "fields": {

    "parent": {"key": "{{triggerIssue.key}}"}

  }

}

Not sure whether it is the trigger issue or something else that is causing the trigger to happen so you might need to tweak that. 

Thanks for answering. I tried couple of things but, not yet with success.

I have found out that Parent link from Advanced roadmaps is a customfield and I know the ID "customfield_13100".

 

when I use your code, replacing "parent" by "customfield_13100" it should work.

Assuming that {"key": " {{triggerissue.key}}"}. means: fill the customfield with the value of the key from the issue that triggers creating the new issue, Resulting the new issue to have the trigger issue as its parent.

 

{
"fields": {
"customfield_13100": {"key": "{{triggerissue.key}}"}
}

 

this is the error messasge. I get:

this is the error message I get: 

"Error creating issue
Operation value must be a string "(customfield _13100)""

I did try again with:

{
"fields": {
"Parent link": "{{triggerissue.key}}"
}
}

 

It works. 

Like John Funk likes this
John Funk
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Apr 05, 2023

Great! Glad you got it working. 

Like jeroen_wilmes likes this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events