[#JRA-5052] Allow different "Clone Issue" options

JIRA

Allow different "Clone Issue" options

Created: 25/Oct/04 06:31 PM Updated: 08/Jan/08 03:04 PM

Component/s:

Web interface

Affects Version/s:

3.0.2

Fix Version/s:

None

Time Tracking:

Not Specified

Issue Links:

Part

This issue incorporates:

JRA-9823 Allow to optionally clone an issue's attachments when cloning an issue.

JRA-7561 Provide option to leave subtasks closed when cloning issue with subtasks

~~JRA-9649~~ Clone Issue should ask whether to clone sub tasks

~~JRA-3742~~ Enable clone issue to also clone subtasks.

~~JRA-3766~~ Subtasks cannot be cloned.

Reference

This issue relates to:

JRA-14236 Provide option to only clone open subtasks when cloning an issue

JRA-4821 Clone issue should copy comments, due dates etc.

~~JRA-9650~~ It should be possible to specify whether to clone Issue links when an issue is cloned

~~JRA-9649~~ Clone Issue should ask whether to clone sub tasks

This issue is related to:

JRA-5417 Modify System/Custom Fields when copying an issue

JRA-1558 Clone Issues between projects

JRA-13433 Sub Task should inherit Workflow Status

JRA-12059 Bulk Copy (clone+move) Issues to Multiple Projects

~~JRA-7737~~ Cloning an issue should have an extra step - it should take you to the edit issue screen before saving the cloned issue.....

Participants:	Adam Cameron, Andrew Michalec, Anton Mazkovoi [Atlassian], Brian Krueger, Brian Nguyen, Carole Feugeas, Christoph Enzinger, Evelin Richter, Grigori Karlik, Jeff Turner [Atlassian], John Taber, Polycom, Robert Christensen and smirks
Since last comment:	50 weeks, 6 days ago
Labels:

Description

« Hide

The new clone functionality is very useful. It would be really great if we could control what parts of an issue was cloned. For instance:

Clone entire issue (subtasks, comments, worklog, everything)
Clone with subtasks only
Clone without subtasks
Etc.

Hopefully you get the idea.

All

Comments

Work Log

Change History

Sort Order:

Ascending order - Click to sort in descending order

[ Permlink | « Hide ]

Jeff Turner [Atlassian] - 25/Oct/04 07:48 PM

Hi,

What would you prefer to be the default behaviour?

On JRA-4821, the suggestion was made to have checkboxes for the different parts of an issue to be cloned.

[ Permlink | « Hide ]

Robert Christensen - 26/Oct/04 10:06 AM

My preference would be something like a list of checkbox options to Clone.

IE.

Include Subtasks
Include Comments
Include Worklog

[ Permlink | « Hide ]

Brian Krueger - 10/Nov/04 07:35 PM

As a default, I'd say that any field that is required ought to be cloned. This is not currently the case.

[ Permlink | « Hide ]

Andrew Michalec - 14/Jan/05 08:02 AM

It would be also great to be able to change workflow state when cloning.
I have workflow with "closed" state as finite without ability to reopen by anyone. This state was "accepted as is" let me say during acceptance tests.
Within this model cloned issue is put in the same "closed" state without ability to push things forward.

[ Permlink | « Hide ]

Grigori Karlik - 02/Feb/05 06:22 AM

I think the specification of the Clones' status while cloning is an useful feature.

[ Permlink | « Hide ]

Anton Mazkovoi [Atlassian] - 13/Mar/06 06:49 PM

The options to clone sub tasks and issue links will be available in JIRA 3.6. See linked issues ~~JRA-9649~~ and ~~JRA-9650~~

[ Permlink | « Hide ]

smirks - 14/Mar/06 01:55 PM

It would also be delightful to clone an issue INTO ANOTHER PROJECT.

Right now that is one of our most time consuming annoyances with JIRA. We sometimes have the same issue affecting different clients (sometimes with very subtle differences that can be differentiated by a single field change or comment after having cloned the original issue) but right now we have the chore of creating a new issue in a different project and copying & pasting field by field content and then manually adding the link to the original issue.

[ Permlink | « Hide ]

Evelin Richter - 22/May/06 04:23 AM

For me, it´s essential to specify the status of the clone. I don´t want the clones to be "open" automatically. We like to clone issues that have to be tested in 32bit as well as 64bit environments when they arrive in the test departments responsibility. Those issues have a status like "To be tested" and I want them to go on with this status.

Maybe it´s easiest to allow a choice between the clone as it is now and "Clone everything".

[ Permlink | « Hide ]

Brian Nguyen - 04/Jun/06 09:47 PM

Hi,

Thanks for your feedback. We will certainly take your comments into account when considering this issue.

Thanks,
Brian

[ Permlink | « Hide ]

Carole Feugeas - 02/Mar/07 02:52 AM

Any news about this issue ?
It will be very usefull if we can choose the fields we want to clone, and also the customs fields.
Many thanks

[ Permlink | « Hide ]

Adam Cameron - 02/Mar/07 03:13 AM

I agree strongly with this. It's a right PitA that clone doesn't actually do the complete job. I'd settle for it copying everything (without options not to), and I can manually get rid of the stuff I don't want from the cloned issue.

[ Permlink | « Hide ]

John Taber - 15/May/07 06:23 PM

I'm not sure if anyone mentioned this so I'll chime in.

Email notifications are sent before the issue has been updated because of this issue.

For example, on our setup emails are sent when issues are created. When issues are cloned this is what happens.
1) User finds an issue they want to clone.
2) They hit the clone button. The small dialog appears and they set a new summary. (Instead the user should simply be brought to a new issue screen with all the existing data populated.)
3) The user hits the button to continue. << The issue is created and the notification is sent BEFORE any other changes are made. The issue can not be updated before the notification is delivered.

[ Permlink | « Hide ]

Christoph Enzinger - 18/May/07 10:26 AM

My preference would be something like a list of checkbox options to Clone.

<p>Include
<ul>
<li>Subtasks
<li>Comments
<li>Worklog
<li>Workflow Status
<li>Attachments
<li>User defined fields
</ul>

[ Permlink | « Hide ]

Polycom - 30/Jul/07 03:28 PM

Adding a vote for Polycom. We would like to see this feature in JIRA. An extended 'clone' feature should provide the ability to select whether to copy attachments, comments and even change history.