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 rule to propagate specific label from epic to child issue not working

Evelyn Ramberger

Hi ,

I am trying to set up an automation rule that gets triggered whenever an issue is created. If the epic that the issue is created in has the label "test", I want the issue to also receive the label "test" (I do not want to copy the other labels)

While this didn't seem complicated to set up, it's unfortunately not working for me.
I checked the JQL query when setting up the rule and it found the epic with the label "test". However, the label did not get propagated when I created a task within the epic. In the rule audit log, I can see that the "issue did not match the condition ". It looks like

I already tried setting the JQL query to "parent", this did not change the performance

Any idea what I could do ? Any help is highly appreciated!

Screenshot 2023-11-02 at 14.24.00.png

Accepted answers

Bill Sheboy

Hi @Evelyn Ramberger

That Issue Created trigger can fire so quickly that the issue's data is not yet available to the rule. And so the actions / conditions / branches do not work as expected.

The work-around is to always adding the Re-fetch Issue action immediately after that trigger. It will slow the rule by about a second and reload the data before proceeding with the other steps.

Kind regards,
Bill

All comments

David Blank

Hi @Evelyn Ramberger and welcome to the Atlassian Community!

This all looks good to me! Can you show us your Action to see if there could be something there?

David Blank

I was able to get it to work in my organization like this:

Screenshot 2023-11-02 at 12.03.48 PM.png

Evelyn Ramberger

Hi David, thank you for your response!

I set up the action like this

Screenshot 2023-11-02 at 17.08.09.png

I also just tried setting this up the same way as you did but it still does not work

Screenshot 2023-11-02 at 17.12.44.png

I keep seeing in the log that the issue did not match the condition; but the issue number is the number of the created issue and not the associated epic (Jira should be looking for the label in the epic not in the issue)

Evelyn Ramberger

it seems that Jira is not looking up the issue in the related issue (although it is specified like this in the rule)

Bill Sheboy

Hi @Evelyn Ramberger

That Issue Created trigger can fire so quickly that the issue's data is not yet available to the rule. And so the actions / conditions / branches do not work as expected.

The work-around is to always adding the Re-fetch Issue action immediately after that trigger. It will slow the rule by about a second and reload the data before proceeding with the other steps.

Kind regards,
Bill

Evelyn Ramberger

thank you @Bill Sheboy this is much better than the workaround I set up!

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-software

jira-software-cloud