Loading...

XML

Word

Printable

Details

Type: Suggestion
Resolution: Unresolved
Fix Version/s: None
Component/s: Issue - Actions
Labels:

UIS:
124
Support reference count:
34
Current Status:
Hide

Atlassian Update – 10 September 2018

Hi everyone,

Thanks for your interest in this issue.
This request is considered a potential addition to our longer-term roadmap.

We'll typically review this request in about 12 months time, at which point we’ll consider whether we need to alter its status.

For the nearest future we've decided to prioritize other areas of the Jira Server roadmap, including:

Performance and stability improvements

Improving performance of boards

Improving Jira notifications

Creating an email template editor

Mobile app for Jira Server

You can learn more about our approach to highly voted server suggestions here.

To learn more on how your suggestions are reviewed, see our updated workflow for server feature suggestions.

Kind regards,
Jira Server Product Management
Show
Atlassian Update – 10 September 2018 Hi everyone, Thanks for your interest in this issue. This request is considered a potential addition to our longer-term roadmap. We'll typically review this request in about 12 months time, at which point we’ll consider whether we need to alter its status. For the nearest future we've decided to prioritize other areas of the Jira Server roadmap, including: Performance and stability improvements Improving performance of boards Improving Jira notifications Creating an email template editor Mobile app for Jira Server You can learn more about our approach to highly voted server suggestions here . To learn more on how your suggestions are reviewed, see our updated workflow for server feature suggestions . Kind regards, Jira Server Product Management
Feedback Policy:

We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

Description

8NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

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 with new reporter
Clone without subtasks
Clone linked issues
Etc.

Hopefully you get the idea.

Attachments

Issue Links

incorporates

JRASERVER-3742 Enable clone issue to also clone subtasks.

Closed

JRASERVER-3766 Subtasks cannot be cloned.

Closed

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

Closed

JRASERVER-9649 Clone Issue should ask whether to clone sub tasks

Closed

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

Closed

JRASERVER-26782 Cloning Sub-tasks does not clone comments

Closed

is duplicated by

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

Closed

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

Closed

JRASERVER-20546 When watched errors are cloned, the new=cloned error shall be automatically watched as well.

Closed

JRASERVER-21369 Do not keep data from custom date fields when cloning

Closed

JRASERVER-22595 Separate clone issue permission

Closed

JRASERVER-23847 Improvements to Issue Cloning feature, by optionally allowing user to move cloned issue to another project, link cloned issue and edit issue fields, before clicking "Create"

Closed

JRASERVER-24613 Enable possibility to set/change/keep current reporter/assigne when cloning an issue and also have the ability to point the clone to a different project than the project for the original issue

Closed

JRASERVER-24830 Add ability to edit the prefix for subtasks when being cloned.

Closed

JRASERVER-70683 Clone issue should copy comments, due dates etc.

Gathering Interest

is incorporated by

JSWSERVER-7721 When cloning an Epic, add the option to clone the linked Stories as well

Future Consideration

is related to

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

Closed

JRASERVER-13433 Sub Task should inherit Workflow Status

Closed

JRASERVER-16511 Cloning should have an option to clone the linked issues

Closed

JRASERVER-1558 Deep copy an issue to the same project or a single project

Gathering Interest

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

Gathering Interest

relates to

JRASERVER-9649 Clone Issue should ask whether to clone sub tasks

Closed

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

Closed

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

Closed

JRASERVER-37848 Clone issues should not capture the current date time

Closed

JRACLOUD-5052 Allow different "Clone Issue" options

Gathering Interest

JRASERVER-1558 Deep copy an issue to the same project or a single project

Gathering Interest

was cloned as

JRASERVER-68054 Allow different "Clone Issue" options

Closed

mentioned in: Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...

(1 incorporates, 9 is duplicated by, 1 is incorporated by, 5 is related to, 6 relates to, 1 was cloned as, 7 mentioned in)

Activity

People

Assignee:: Unassigned

Reporter:: Robert Christensen

Votes:: 502 Vote for this issue

Watchers:: 287 Start watching this issue

Dates

Created:: 25/Oct/2004 11:31 PM

Updated:: 11 hours ago