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.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I have an automation that runs if a parent link is added, changed, or removed from an issue.
My main problem :
When I create an issue from an EPIC, it seems, that it both creates and edits the issue. so.. the rule runs twice.
I created separated automations for creating and editing issues, and it confirmed the behaviour..
the rune is rules once for creation and once for edition when creating an issue directly from an Epic.
Also... when I create an issue without linking it from scratch to an Epic, I get an error.
Some help on that would be much appreciated.
I have seen this symptom noted in a few other posts: issue linking does not occur at the time of issue create, and instead happens as a separate edit. This happens for manual issue creation and by automation rules.
Which is curious as the REST API does support adding one link, but not several. And so that is probably why this design was used. There is an open defect / suggestion to allow adding multiple links during issue create: https://jira.atlassian.com/browse/JRACLOUD-81845
So on to work-arounds...
One way to solve this is to remove the Create Issue selection from the trigger. For your scenario you want to perform the same action for create and edit, and so eliminating the create selection should solve the double rule execution.
However, I notice some things in your rule and wonder:
Essentially, are you trying to sync the labels from the parent down to children, or only perform the one-time set of values?
Hi @Bill Sheboy
Thank you for your reply.
Indeed, deactivating the "creation" trigger helps ! I am ashamed I didn't think about it 😅
To answer your last questions :
Yes, I am trying to sync the labels from the parent down to children. But as the parent might never change.. it is ok to do it this way. But if you have a better way, I would be more than happy to learn it.
I am glad to learn that helped...and apologies in advance for my long, follow-up answer :^)
Sync of fields is not something built-into Jira. And so it helps to consider the different scenarios, and which ones you want to address...