• 13
    • 59
    • We collect Jira Service Desk 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 Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding suggestion.

      At present, Project Import functionality does not currently include Active Objects data and so it is not possible to move JIRA Service Desk project data between instances. https://confluence.atlassian.com/display/JIRA/Restoring+a+Project+from+Backup

      As an administrator, I would like the ability to import a Service Desk project from XML backup. This would allow me to move a Service Desk project from one instance of JIRA to another.

      • The import needs to include JSD custom fields and Active Objects data so that my Service Desk configuration, SLAs, and request types will be imported.

          Form Name

            [JSDSERVER-2741] Provide the ability to import a Service Desk project from an XML backup

            Sampath added a comment -

            Sampath added a comment - https://getsupport.atlassian.com/browse/PSSRV-59829  

            The Project Configurator add-on for Jira has the capability to backup and restore Service Desk configuration (request types, SLAs, portal settings, etc.).

            Jeffrey Thornsen added a comment - The Project Configurator add-on for Jira has the capability to backup and restore Service Desk configuration (request types, SLAs, portal settings, etc.).

            Hi,
            the request was raised in 2015 - is there any update on this?

            Thanks

            Ala

            Alicja Rudnicka added a comment - Hi, the request was raised in 2015 - is there any update on this? Thanks Ala

            When importing a project, validation complains about ServiceDesk specific custom fields which does not support import.

            In case of "big" mistakes in a project (deleted issue, misconfiguration...), "import" is the only way to fix them without impacting the whole JIRA instance and other projects.

            Yves Martin added a comment - When importing a project, validation complains about ServiceDesk specific custom fields which does not support import. In case of "big" mistakes in a project (deleted issue, misconfiguration...), "import" is the only way to fix them without impacting the whole JIRA instance and other projects.

            Any updates on this feature request? When would be the roadmap for this to be implemented?

            Ramhya Ravichandran added a comment - Any updates on this feature request? When would be the roadmap for this to be implemented?

            This is a limitation of JIRA, as it is currently not possible to import a project that includes plugins that use ActiveObjects tables.

            The workaround at the moment would be to perform a full system import, if that is a possibility in circumstances.

            Matthew McMahon (Inactive) added a comment - This is a limitation of JIRA, as it is currently not possible to import a project that includes plugins that use ActiveObjects tables. The workaround at the moment would be to perform a full system import, if that is a possibility in circumstances.

              Unassigned Unassigned
              tevans Tim Evans (Inactive)
              Votes:
              138 Vote for this issue
              Watchers:
              80 Start watching this issue

                Created:
                Updated: