-
Suggestion
-
Resolution: Unresolved
-
92
-
45
-
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? 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.
- is related to
-
JRACLOUD-12059 Bulk Copy (clone+move) Issues to Multiple Projects
- Closed
-
JRACLOUD-28038 Be able to clone watchers
- Closed
-
JRACLOUD-7948 Ability to Create issues and automatically Clone/Move to multiple projects and maintain changes across Cloned issues
- Gathering Interest
-
JRASERVER-1558 Deep copy an issue to the same project or a single project
- Gathering Interest
- relates to
-
JRACLOUD-37849 Clone an issue that was cloned from another issue, does not give the "Clone Links" checkbox
- Closed
-
JRACLOUD-5052 Allow different "Clone Issue" options
- Gathering Interest