-
Suggestion
-
Resolution: Unresolved
-
493
-
132
-
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
Hi everyone,
Thanks so much for your votes and comments on this feature request. While this feature is something we want to add to JIRA, it is not on the list of priorities for the next 12 months.
In the meantime, please check out these plugins:
on our Atlassian marketplace. Both of these plugins are available for the downloaded instances of JIRA and solve the use cases outlined in this requirement.
There's also another solution emerging from an Atlassian Exper Catworkx.de. You can check out the factsheet here
Thanks for your patience and we hope you appreciate our open and honest approach to feature requests.
Chur,
Otto Ruettinger
JIRA Principal Product Manager
oruettinger (at) atlassian (dot) com
Original request description
Needed features:
- Import / export a project's structure (incl. workflow, related issue types, related groups, permissions, screens, fields, field configurations, etc.), but not its issues or history. This is useful to copy from the test installation of jira into the productive one.
- Delete all issues and history of a project, but not its structure. Delete all closed issues of a project and their history, but not it's structure. This is useful for test purposes and for cleaning purposes in case of changes that make the old issues not required to read but useful to archive (e.g. for legal needs).
- Import / export / delete a complete project, structure and issues. This is useful for backup flexibility and data cleanup (each dept. of the concern keeps its own data; When Maintenance have made a mistake and need to restore their backed-up data, we don't want to restore Development's data as well).
As a workaround for the lack of these features, we happen to use several installations for test purposes. But our managers definitely won't allocate any money for the corresponding licences, since juggling with several instances of a program is neither efficient nor convenient.
Moreover, for now we end up with either databases full of unneeded, outdated test data, or with hours of click-click-click-copying a project's structure from the test system into the productive environment. (We tried direct manipulation of XML export data or databases, unsuccessfully.)
Workaround
Use the Cloud-to-cloud migration (beta) tool
See the article What migrates in a cloud-to-cloud migration for Jira for more information
- is duplicated by
-
- Closed
-
- Closed
- is related to
-
- Closed
-
- Gathering Interest
- causes
-
CES-46041 You do not have permission to view this issue
-
PCS-308041 Loading...
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JRACLOUD-7641] Export / Import configuration information/data
This is long overdue - and I wholly agree with the comment below.
We should not need to purchase a third party plugin for a feature that should be native to the tool. If this is supposed to be a tool geared towards developers, and it's a developer centric platform - this is something that would enable config as code. We would be enabled to configure as code in lower environments, version control the config and promote to necessary environments as needed. This needs to be built.
Since there is no sanitize option available in Jira, our Sandbox becomes populated with Production data after import, posing a security risk. Our preference is to exclusively import projects/configurations from Jira without including any data in the Sandbox environment.
If this alternative is not viable, the only recourse would be to import the full backup into the Sandbox and subsequently undertake the arduous and impractical task of manually deleting each issue one by one.
Would love this function as an enterprise user and having multiple instances would love to be able to move the config from instance to instance.
The apps that are offered by 3rd parties are not working great so manually doing this is a pain.
Thanks
Hi Lisa,
You can do that with Project Configurator for JIRA. Choose "Configuration only" when selecting scope for the export and "Import project configuration" for importing and that way you will not move issues or attachments. When importing, you can select to exclude some items from import, like workflows or workflow schemes.
Cheers,
José Marañón
Awnaba Software S.L.
I would like to be able to import/export non-workflow schemes such as customized issue types, issue type schemes, issue field configuration schemes, and issue type screen schemes. We would like to import them into the new projects under our Enterprise-wide solution or into a closed system (not on the network for security reasons). I realize you can export/import issues but we do not want to populate existing issues from one project into a new project, we want to take advantage of their schemes (not workflow – I know you have import/export for workflows).
Lisa
Hi everyone,
Thanks so much for your votes and comments on this feature request. While this feature is something we want to add to JIRA, it is not on the list of priorities for the next 12 months.
In the meantime, please check out these plugins:
on our Atlassian marketplace. Both of these plugins are available for the downloaded instances of JIRA and solve the use cases outlined in this requirement.
There's also another solution emerging from an Atlassian Exper Catworkx.de. You can check out the factsheet here
Thanks for your patience and we hope you appreciate our open and honest approach to feature requests.
Chur,
Otto Ruettinger
JIRA Principal Product Manager
oruettinger (at) atlassian (dot) com
A great feature : import workflow or display a preview into whiteboard Confluence.