Details
-
Suggestion
-
Resolution: Unresolved
-
None
-
11
-
8
-
Description
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
Hi all,
Thanks for participating in this issue, either by voting, commented or just watching. We highly value your feedback in all forms, and through suggestions in jira.atlassian.com is not different. We use this channel often to learn the best we can with how customers use JIRA and how we can continue to improve the experience for as many users as possible.
At this time, this suggestion is not on the JIRA development roadmap. There a couple add-ons on the Atlassian Marketplace that can support this, such as Configuration Manager for JIRA. Alternatively, this is very easy to do with a simple GET of the component you want to copy and a POST of the components JSON representation to the JIRA REST API, simply change the project key and id in the rep.
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,
Kerrod Williams
Kerrod (dot) Williams (at) atlassian (dot) com
Product Manager, JIRA
This issue is related to JRE-501 (Shared Components) and JRE-6999 (Add ability to export/import projects):
We need a way to copy components from one project to another. This is because the projects have nearly the same components.
There are several ways how this issue might be solved from my point of view:
1. There might be an ex- and import of project-components.
2. There might be a button in the Projects-Administration to copy a project.
3. Upon creation of a new project you are asked if to take components from an existing project (and perhaps other settings, too)
Now the reason why we require this:
In contrast to perhaps the normal application-development we had to create projects for each release-version of the same application. This is because after a version is released it will go into maintenance-mode thus the version is never really finished. See for example a release history like this:
January V 1.0 build 1 Final-Release (Components: A, B, C)
February V 1.1 build 1 Final-Release (Components: A, C)
March V 1.0 build 2 Bugfix-Release
April V2.0 build 1 Final-Release (Components: A, C, D)
May V1.1 build 2 Bugfix-Release
and so on. Therefore virtually we have a new project/product with every Final-Release. It's rather hard to mirror this pre-existing handling of versions inside JIRA as the "normal" version-concept included into JIRA does not fit. So the application-versions are now projects while the JIRA-version-field is related to the build-numbers.
To use our workaround we now have to copy all components from one project to another. Resolving this issue would ease to handle this workaround.
Attachments
Issue Links
- relates to
-
- Closed
-
- Gathering Interest
-
- Not Being Considered