nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Original Estimate copied during cloning? Can we omit?

Kim P

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.

Accepted answers

Chris Buzon

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/

All comments

Chris Buzon

Kim P

Thanks for confirming!

mummareddy supriya

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

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud