nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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

jeroen.wilmes

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.

Accepted answers

John Funk

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.

All comments

John Funk

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.

jeroen.wilmes

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.