I'm noticing that during cloning, the original estimate value is carried to the cloned issue. Is this the expected behavior? Is there any way to omit it from copying?
*I am aware I can create an automation rule to clear the field after clone is complete.
That's expected, you get very limited options when it comes to Cloning. Atlassian itself suggests using Automation to fix up things after the fact.
Just after you hit the CLONE button, the options you are allowed to ignore are presented. They are quite limited, unfortunately. (at least in Cloud)
https://support.atlassian.com/jira-software-cloud/docs/clone-an-issue/
Clone Epic Function - Story/Review Sub-task Field Clearing Problems
While cloning any issue the estimates and checklist will be carried over, which should not be like that.estimates and checklist list items should not be taken over during clone operation.please provide me solution for this
if any one having idea please suggest me the solution for this
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.