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; } } }

Link issue to existing EPIC - JIRA Automation

jvantrease

Hello,

I am attempting to create a rule that edits the epic link and assigns a specific epic to that issue. I am using the following JSON

{

"fields": {

"Epic Link": "ISSUE_ID_OF_EPIC"

}

I receive an error stating

Edit issue

Error editing issues

SomeIssue-160 (Issue 'ISSUE_ID_OF_EPIC' must be of type 'Epic'.)

The issue shows up as an epic. I think I am missing something. Any help would be appreciated. Thank you.

Accepted answers

Stefan Salzl

Hi @jvantrease and welcome to the community,

Some questions:

In your screenshot it seems your action is in another "line" (like it would be if there is a branch in between). Is that the whole automation rule? If not please provide complete material for the community to be able to do a propper analyze.
you mentioned "ISSUE_ID_OF_EPIC" --> did you write the issueID or the issueKey into your JSON? I tested with adding the issue key to a JSON and it worked like a charm.
eg.:
If you added the key in your JSON please provide a clear screenshot of your JSON as well as from the issue you are trying to link.

Best
Stefan

All comments

David Pezet_yyhi7z

You might try passing the entire issue instead of just the key. If you only have the key to work with, you could use a lookupIssues action to get the issue based on the key. This returns a list, so you will probably need to reference it as {{lookupIssues.first}} to return the whole issue.

David Pezet_yyhi7z

Oh sorry! I just saw that you have both the Epic Link field and Epic Link in the Additional fields section. This could also cause problems. You'll want to uncheck that in the dropdown when using the Additional fields.

Stefan Salzl

Hi @jvantrease and welcome to the community,

Some questions:

In your screenshot it seems your action is in another "line" (like it would be if there is a branch in between). Is that the whole automation rule? If not please provide complete material for the community to be able to do a propper analyze.
you mentioned "ISSUE_ID_OF_EPIC" --> did you write the issueID or the issueKey into your JSON? I tested with adding the issue key to a JSON and it worked like a charm.
eg.:
If you added the key in your JSON please provide a clear screenshot of your JSON as well as from the issue you are trying to link.

Best
Stefan

jvantrease

Hello Stefan,

Thanks so much for your help. I eventually figured out the issue. The issue I was trying to link was not an Epic issue. It was in fact a User journey. Sorry to bother you.

Stefan Salzl

That would have been my main guess

Good to know you got that working and thanks for your feedback

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

automation