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 changes an issue type (A to B) and then clones the issue to a new project. The issue on the new project board has the original value (A) for issue type even though it is cloned after the change is done.
I did a display of that value and sure enough it is set as A even though the change has been done. When the automation finishes the original ticket has the new value of B.
Is the changed field value not available until after the automation has completed - like a commit?
Hello @Dave Symonds ,
I was able to replicate your behavior and was able to resolve it by adding a Re-fetch issue data action before the Clone issue action:-
Give it a try and let us know how it goes.
Hope this helps.
I suggest not editing the issue type with an automation rule, but instead perform a clone to the new type and then abandon (or delete) the original issue.
Changing an issue type is a complicated operation that can run into problems due to differences of fields, workflow, parent/child relationships, etc. This is one reason the Jira UI has a specific function to do this: Move. That allows the move to ask any necessary questions to ensure success, or to prevent the move when it is not possible.
An automation rule can do none of those things. And so a work-around for rules is to clone and use a new issue type for the issue.