• 394
    • 150
    • Hide
      Atlassian Update –

      20 March 2018
      Hi everyone,

      Thanks for your interest in this issue.
      This request is considered a potential addition to our longer-term roadmap.

      We'll typically review this request in about 12 months time, at which point we’ll consider whether we need to alter its status.

      For the nearest future we've decided to prioritize other areas of the Jira Server roadmap, including:

      • Performance and stability improvements
      • Archiving projects for improved performance
      • Optimising the use of custom fields
      • Improving performance of boards
      • Improving Jira notifications
      • Allowing users to edit shared filters and dashboards
      • Mobile app for Jira Server

      You can learn more about our approach to highly voted server suggestions here.

      To learn more on how your suggestions are reviewed, see our updated workflow for server feature suggestions.

      Kind regards,
      Jira Server Product Management

      Show
      Atlassian Update – 20 March 2018 Hi everyone, Thanks for your interest in this issue. This request is considered a potential addition to our longer-term roadmap. We'll typically review this request in about 12 months time, at which point we’ll consider whether we need to alter its status. For the nearest future we've decided to prioritize other areas of the Jira Server roadmap, including: Performance and stability improvements Archiving projects for improved performance Optimising the use of custom fields Improving performance of boards Improving Jira notifications Allowing users to edit shared filters and dashboards Mobile app for Jira Server You can learn more about our approach to highly voted server suggestions here . To learn more on how your suggestions are reviewed, see our updated workflow for server feature suggestions . Kind regards, Jira Server Product Management
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

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

      In order to move a project between two different instances, an user must export a whole XML backup from the source instance, and will only import one project in the target.

      For huge instances, where there are over 400 projects, exporting a full XML backup may result in performance issues during the time it takes for the backup to complete, and as exporting all 400 projects is not necessary to only import one project, it would be good if it was possible to export only one single project to be imported into another instance.

          Form Name

            [JRASERVER-34307] Add the ability to export/import a single project

            Please add export / import for a single projects. 

            Kind Regards.

            Florin

            Florin Iovi added a comment - Please add export / import for a single projects.  Kind Regards. Florin

            ray.garcia added a comment -

            It's kind of unbelievable this is not default functionality but it can be done with a commercial plugin. You have my strong vote to add this on the roadmap, but since it's from 2018 I assume that if didn't happen over the last 5 years maybe it will happen never.

            ray.garcia added a comment - It's kind of unbelievable this is not default functionality but it can be done with a commercial plugin. You have my strong vote to add this on the roadmap, but since it's from 2018 I assume that if didn't happen over the last 5 years maybe it will happen never.

            Yes.  Please add export / import single projects.  

             

            Randy Taylor added a comment - Yes.  Please add export / import single projects.    

            I've today re-installed from scratch my test Jira environment.
            As I don't want to keep on updating all system settings and the likes, I'd like to be able to copy a subset of my prod to test.
            For this, I want to be able to import only some projects : My projects templates (I have two : Kanban & Scrum along with permission schemes, workflows...)

            The other way around is also a big bonus, being able to develop new things on test and copy them to production later on.

            Rudy Dullier added a comment - I've today re-installed from scratch my test Jira environment. As I don't want to keep on updating all system settings and the likes, I'd like to be able to copy a subset of my prod to test. For this, I want to be able to import only some projects : My projects templates (I have two : Kanban & Scrum along with permission schemes, workflows...) The other way around is also a big bonus, being able to develop new things on test and copy them to production later on.

            Cheer UP!

            shivamdu added a comment -

            Appreciate if this feature can be implemented in the upcoming versions (Server and Cloud). This would definitely be a very useful feature. The place where i work, we have two environments and projects are setup in the lower environment first for proofing and then it is setup in PROD. Now we have been doing dual work since we don't have this feature to export the project seperately!

             

            Thanks in advance!

            shivamdu added a comment - Appreciate if this feature can be implemented in the upcoming versions (Server and Cloud). This would definitely be a very useful feature. The place where i work, we have two environments and projects are setup in the lower environment first for proofing and then it is setup in PROD. Now we have been doing dual work since we don't have this feature to export the project seperately!   Thanks in advance!

            This would be a great feature for us. We have amassed a very large database over the many years of using Jira and we are now in a bad position thinking of moving to the Cloud and not sure we can do it.  If we could move just the projects we want to move forward with and backup the others that would be ideal.

            Also, when we need Support it is difficult for us.

            Anne Gallant added a comment - This would be a great feature for us. We have amassed a very large database over the many years of using Jira and we are now in a bad position thinking of moving to the Cloud and not sure we can do it.  If we could move just the projects we want to move forward with and backup the others that would be ideal. Also, when we need Support it is difficult for us.

            The story I heard at the last Atalassian conference is "we are a cloud first company".  If this is true why wouldn't you make it easier for your customers to move individual projects from Server to Cloud so you have more customers in the Cloud?

            James L Cleckler added a comment - The story I heard at the last Atalassian conference is "we are a cloud first company".  If this is true why wouldn't you make it easier for your customers to move individual projects from Server to Cloud so you have more customers in the Cloud?

            Phil Gran added a comment -

            It would be sweet if you guys could do this, but I imagine it is a ton of work.

            Phil Gran added a comment - It would be sweet if you guys could do this, but I imagine it is a ton of work.

            Apart from the labour and performance considerations sometimes there's also a permissions requirement.

            It should be possible for project admins to export their single Jira project including issue history, meta data, structure and configuration, so that the project can be replicated (moved) to another established Jira instance.

            Neil Gulati added a comment - Apart from the labour and performance considerations sometimes there's also a permissions requirement. It should be possible for project admins to export their single Jira project including issue history, meta data, structure and configuration, so that the project can be replicated (moved) to another established Jira instance.

              Unassigned Unassigned
              mfernandes@atlassian.com Matheus Fernandes
              Votes:
              642 Vote for this issue
              Watchers:
              348 Start watching this issue

                Created:
                Updated: