I have an automation that is supposed to copy some fields when an issue is created if the linked issue (where it's getting cloned from) is in a certain project. I think there's a timing problem where the link isn't present at the time the rule gets run so the fields aren't copying.
Now I'm trying to create an automation that says if the issue transitions from status A to status B then create an issue in a different project and copy fields. BUT, I have two transitions from A to B (already in development/send to development). Only in one of those transitions should the automation run. I cannot figure out how to find the actual transition option, not just the change in status.
Do I have to redo everything (workflow and automation) or is there a way to find the actual transition used and apply it to an automation rule?
Regarding the first rule you note and the timing issues, there are definitely race-track conditions in the automation rules due to the asychronous processing, particularly after the create issue trigger.
One work-around I use is to put a Re-fetch action immediately after the trigger. It does slow the rule down a bit, but it helps to give the issue a chance to fully load before you try to use it.
Catch up with Atlassian Product Managers in our 2020 Demo Den round-up! From Advanced Roadmaps to Code in Jira to Next-Gen Workflows, check out the videos below to help up-level your work in the new ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events