Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JRACLOUD-7641

Export / Import configuration information/data

    XMLWordPrintable

Details

    • 8
    • 74
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

    Description

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

      Atlassian Status as of 21 December 2015

      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.)

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              e5e14e4e5311 Rémy Mouton
              Votes:
              229 Vote for this issue
              Watchers:
              168 Start watching this issue

              Dates

                Created:
                Updated: