Edit the screen scheme for cloned issues

[Deleted user]

When I clone a issue, I wanted to edit certain fields before I clone. ATM, the only thing I could edit is Summary. Is there a way to also add certain fields that I could edit before creating a cloned issue?

[Christos Moysiadis]

From my personal experience this is not possible. Except this, this is the meaning of the word "Clone". The creation of an identical issue as the one before!

regards

CM

[Helder Miguel Alves Magalhães]

For completeness, there's a request for a much broader feature, JRASERVER-5052, and also a tightly related issue, JRASERVER-16574, closed as "duplicate" of the first one.

[Helder Miguel Alves Magalhães]

More recently I've "discovered" about Create linked issue which seems a better fit for use cases like the one being discussed here: ability to edit fields before actually creating. While I'm still experimenting with it, I've already somehow documented a comparison with Clone:

Use Create linked issue instead of Clone

If you use Clone for creating task follow-ups or related tasks, copying tasks between projects (i.e., create a team internal work item from a support project), then Create linked issue is your friend: It will do that but... Better!

Create linked issue features the following improvements:

• Inherits Summary, Description and most fields as the original issue
  • 🫱 Similar to Clone
• A link to the original one
  
  • 👍 Avoids crawling/copy+paste/errors when intending to create a bound to the original issue (better than Clone)
• Reporter set to the current user
  • 👍 Not to the original issue reporter (an undesired and quite annoying side-effect of Clone)

^{Create linked issue is available in the issue detail menu More drop-down (same as Clone).}

Because a colleague has noticed that (unexpectedly) Completed Sprints are copied without an option (unlike Clone), I'm also leaving the follow-up for those cases:

Apparently Clone issue does have an option to discard this date due to "popular demand". Using Create linked Issue there's a workaround proposal:

Remove the sprint value from its field via JIRA issue navigator bulk edit:

1. search for the affected issues in the Issue Navigator;
2. click Tools > Bulk Edit;
3. select the issue and click Next, then select Edit Issues and click Next;
4. select Change Sprint and edit the value accordingly - if you don't want the issue to be associated with any sprints, leave the field empty;
5. click Next and proceed with the instructions to complete the change.

Source: [JSWSERVER-10548] Cloned issues inherit the Completed Sprint value and can't be removed (Workaround 1)