-
Suggestion
-
Resolution: Unresolved
-
None
-
13
-
30
-
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
Hi everyone,
Thanks for voting and commenting on this issue. Your feedback is key to helping us understand how you use JIRA so we can continue improving your experience. We have reviewed this issue over the last few days; unfortunately we don't have any plans to support this in JIRA for the foreseeable future. There are a large number of add-ons available in the Atlassian Marketplace that provide this feature.
Please remember that jira.atlassian.com is one of many inputs for the JIRA roadmap. You can learn more about our process here.
I understand that our decision may be disappointing. Please don't hesitate to contact me if you have any questions.
Regards,
Dave Meyer
dmeyer@atlassian.com
Product Manager, JIRA Platform
Original request description
As JIRA users we want the ability to copy / clone JIRA issues between multiple projects in such a way that all information related to the issue being copied is retained, specifically: summary, description, comments, labels, assignee and reporter, versions and components plus all the content stored in the custom fields.
- duplicates
-
JRASERVER-750 Move issues between projects
- Closed
- incorporates
-
JRASERVER-833 Promote comment to issue
- Closed
- is blocked by
-
JRASERVER-12059 Bulk Copy (clone+move) Issues to Multiple Projects
- Gathering Interest
- is duplicated by
-
JRASERVER-11119 Is it possible to "import" an XML extract that was generated by JIRA (please read "DESCRIPTION" for more details)
- Closed
-
JRASERVER-5891 Copying of issues from one project to another
- Closed
-
JRASERVER-1469 Prefill Create Issue details with the details of the last issue entered
- Closed
-
JRASERVER-2135 Ability to copy on incident
- Closed
-
JRASERVER-2452 Repetitive issues
- Closed
-
JRASERVER-9071 Copy issue instead of move - leave old issue in place, generate new, create link automatically
- Closed
-
JRASERVER-12178 Create a macro to allow an automatic clone and move of an issue
- Closed
-
JRASERVER-12315 Move Issue should create the new issues in the initial workflow status.
- Closed
-
JRASERVER-24837 The ability to clone and move an issue
- Closed
- is related to
-
JRASERVER-9564 Add JIRA move issue workflow post-function
- Closed
-
JRASERVER-28038 Be able to clone watchers
- Closed
-
JRASERVER-7948 Ability to Create issues and automatically Clone/Move to multiple projects and maintain changes across Cloned issues
- Gathering Interest
-
JRASERVER-12059 Bulk Copy (clone+move) Issues to Multiple Projects
- Gathering Interest
-
JRASERVER-5052 Allow different "Clone Issue" options
- Future Consideration
- relates to
-
JRASERVER-648 Created linked issue
- Closed
-
JRASERVER-4821 Clone issue should copy comments, due dates etc.
- Closed
-
JRASERVER-9564 Add JIRA move issue workflow post-function
- Closed
-
JRASERVER-17190 Creating issues based on another issue
- Closed
-
JRASERVER-37849 Clone an issue that was cloned from another issue, does not give the "Clone Links" checkbox
- Closed
-
JRACLOUD-1558 Deep copy / clone an issue to the same project or a different project
- Gathering Interest
-
JRASERVER-70683 Clone issue should copy comments, due dates etc.
- Gathering Interest
-
JRASERVER-5052 Allow different "Clone Issue" options
- Future Consideration
-
PS-18460 Loading...
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Wiki Page Loading...