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

Automation to update epic when issue is created

SParker

Hello all,

I am trying to use the automate feature within Jira cloud to do some conditional operations when an issue is created. I want to check the description field to see if a couple different values are found. If one of the values is located, then to assign the appropriate epic to that issue. I am having no luck and can't see to get the update to occur even though the JQL that I have comes back with the match I expect. Below is a section of the automation that I am using. I have three sections that are identical except for the description value and the epic link they correspond to.

Any help would be greatly appreciated.

Close up of the Edit issue fields section:

Accepted answers

All comments

Bill Sheboy

Hi @SParker

Is this a classic or next-gen project? I recall seeing somewhere that the Epic Link field is no longer used for next-gen projects to manage the parent/child linking.

If this is a classic project, you may want to put in a support ticket as I think what you are trying should work.

Best regards,

Bill

SParker

Thanks for the response Bill. I am in a classic project. I will contact Atlassian and see what they have to say about this and if I am doing something wrong.

Thanks

Vladimir Tarusov_rehi5v

@SParker could you please return with feedback later? I'm also wonder why is this happening. Trying "Epic Name" field but it doesn't work too.

Mehmet A _Bloompeak_

Hi @SParker ,

Below worked on my classic Jira project. Instead of "If issue matches: JQL", I used "Issue fields condition"

Screen Shot 2020-04-29 at 23.12.56.png

SParker

I tried that as well and it didn't work either. I am now working with the instance admin to check all the permissions to see if something is off for the Role Actor.

SParker

Sorry for the late response. There are no errors at all. It is that the entire rule isn't firing all the time. If I make it a global rule, it fires sometimes in other projects, but never for the one I want.

I see that it is firing on some issues, but they are not consistent and never apply the rule as intended. I am attaching a screenshot of what I am seeing in the log.

Bill Sheboy

Hi @SParker

Something I found helpful to resolve rule issues was to add tracing statements to my rule, and then remove them later after I fixed things. You can add comments to find out what values are being used, or use the Log Action or {{Debug}} statements.

https://support.atlassian.com/jira-software-cloud/docs/debug-a-rule/

Best regards,

Bill

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-cloud

addon-com.codebarrel.addons.automation

update

automation