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

Jira Automation Linking an issue on creation to an existing Epic

Ariel Altaras

I am using Jira Data Center. I've created this automation and according to other questions I've read it should work, but I am getting an error each time I create a new issue. I previously tried choosing the Epic Link field in the dropdown, which also had this error, so I switched to the Advanced JSON since I saw that others had success with that.

The rule is limited to a single project, the one containing the referenced Epic. The Epic Link field is present on both the Create and Edit screens for the issue type.

Screenshot 2024-02-29 at 4.23.24 PM.png

Accepted answers

Filipi Lima

Hi, all!

I assisted Ariel and the issue was related to the Actor not having the permission to perform the update.

It's one of the scenarios covered here:

https://confluence.atlassian.com/automationkb/automation-for-jira-reporting-unknown-fields-set-during-edit-they-may-be-unavailable-for-the-project-type-1130727699.html

Cheers!

All comments

John Funk

Hi Ariel,

You should be using the Parent field now instead of Epic Link.

Ariel Altaras

Hi John,

Hmm... I'm on version 9.4.15 and I don't see a Parent field. I do see Parent Link, but when I try to set that I get the following error:

"Unknown fields set during edit, they may be unavailable for the project/type. Check your custom field configuration. Fields ignored -

Parent Link (customfield_15401)"

Also it seems that field is only on the Epic issue type, not the Vulnerability issue type which is the trigger issue.

John Funk

Hmm, surprised that version doesn't have the Parent field. So, yes, I would think you would go with the Epic Link field.

Make sure the Epic Link field is on the Edit screen - that is most likely the error.

Bill Sheboy

Hi @Ariel Altaras

One possible cause of that symptom is the Issue Created trigger can fire so quickly that some of the issue data may not be available for the rule to use.

The work-around / fix is to always add the Re-fetch Issue action immediately after the Issue Created trigger. This will slow down the rule a bit, reloading the issue's data before proceeding with the other steps.

Kind regards,
Bill

Ariel Altaras

The Epic Link field is on both the Create and Edit screens.

Ariel Altaras

Thanks for the tip. I tried adding a Re-fetch, but I'm still getting the same error.

Bill Sheboy

Considering your issue hierarchy, if you manually create an issue of type Vulnerability with the UX page can you set the Epic Link field?

Ariel Altaras

@Bill Sheboy Yes I can, and I can edit a manually created issue to put it under the same Epic. I am actually manually creating the issues to test but not setting the Epic Link field - they are usually created through the API.

Filipi Lima

Bill Sheboy

Thanks, @Filipi Lima !

Welcome!

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

Quick Links

Unanswered
Groups
Help

Find more posts tagged with

automation