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
When you use the Clone Issue action in an automation rule, you have the option to override the value of any fields.
So if you do not want a field to copy from the source issue, just select that field in the action and clear the value. If the field is not shown in the drop-down list, you may use the advanced edit with JSON feature to clear the field.
Please post images of your complete automation rule, including the details of your Clone Issue action, and of the audit log details showing the rule execution. Those may provide context for what you are describing.
Is the rule working as you expect now?
What was the purpose of your condition testing the Due Date?
And...please note the Issue Created trigger can happen so quickly that the data is not yet available to the rule. This can cause conditions and actions to work unexpectedly later in the rule. For example, some of your cloned fields may remain empty
One work-around for that is to always add a Re-fetch Issue action immediately after the Issue Created trigger. This will slow down the rule by about a second and reload the trigger issue's data before proceeding.
yes, the rule is working as expected. I am not sure though why having a condition of "Due date is not empty" would fail it. However, we could survive with always clearing the "Due date" I removed the condition.
I feel, as the rule triggers when issue is created, it is looking at the new issue which is cloned, while i am trying to fetch the data from source ticket data, probably that may be the reason its failing?
Yes, that is correct...as I noted in my last two paragraphs above.
What is happening is sometimes the data is not available after the Issue Created trigger, and so your condition test on Due Date is not empty was not passing. That I why I noted adding the Re-fetch issue after the trigger.
If you are willing to try a third-party app, our Deep Clone for Jira could help you.
With our Clone and Edit feature, you can edit or clear specific field values while cloning issues.
You don't. There's no mechanism for this because cloning means cloning - it is supposed to create a copy of the source issue that is as close to the original as possible, and that means copying all the fields.
No, it's a function of "create issue" - if someone can create an issue in a project, then they can use clone.