Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Original Estimate copied during cloning? Can we omit?

Kim P
Contributor
December 7, 2021

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.

1 answer

1 accepted

0 votes
Answer accepted
Chris Buzon
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
December 9, 2021

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/

Kim P
Contributor
December 14, 2021

Thanks for confirming!

mummareddy supriya
Contributor
May 13, 2024

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

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events