You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Join now to unlock these features and more
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!
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.
I was able to get it to work in my organization like this:
Hi David, thank you for your response!
I set up the action like this
I also just tried setting this up the same way as you did but it still does not work
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)
In my case, in the audit log I do not see the issue key from the epic, I only see the issue that triggered it (created issue) and was subsequently updated:
@Evelyn Ramberger , could it be something with the rule actor? If you look under the Rule Details, you should see who that is. Can you confirm their access? (note: I always use "Automation for Jira" as my actor)
Yes, the scope is equivalent to the project I am triggering from. I think I finally figured out (somehow ) what the issue was. When I created a task within an epic by clicking "create child issue", the task was created but Jira only sets the parent field miliseconds afterwards (I did not change the parent fieldmanually, this must have been triggered by Jira in the background).
But my rule got triggered upon issue creation with an empty parent field. I modified the rule now in the following way and it seems to work.