Uploaded image for project: 'Jira Service Management Cloud'
  1. Jira Service Management Cloud
  2. JSDCLOUD-1317

Ability to copy request types to another Service Management project.

XMLWordPrintable

    • 392
    • 17

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

    • Hide
      Update 15 May 2023

      Please be aware that we have not scheduled any development work on this issue through to the end of the fiscal year 2024 (June).

      However, your input remains incredibly valuable to us. We encourage you to keep voting and providing feedback. Every vote and piece of feedback informs our future priorities and helps us understand your needs better.

      Thank you for your understanding and your continued support.

      Regards,
      Simon
      JSM - Principal Product Manager

      Show
      Update 15 May 2023 Please be aware that we have not scheduled any development work on this issue through to the end of the fiscal year 2024 (June). However, your input remains incredibly valuable to us. We encourage you to keep voting and providing feedback. Every vote and piece of feedback informs our future priorities and helps us understand your needs better. Thank you for your understanding and your continued support. Regards, Simon JSM - Principal Product Manager

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

      Problem Definition

      • In some cases, there are a lot of request types created in a Service Desk project. It's a lot of works for the admins to configure the Request Types on each new Service Desk project.

      Suggested Solution

      • Provide the ability to reuse or copy the request types to another Service Desk project like creating new a project with shared configurations.

      Why this is important

      • Reduce the works when creating new projects
      • Reduce the time needed when managing the projects
      Original Request

      As a Service Desk Administrator, it would be nice if I could copy the request types created in one Service Desk, to another Service Desk.

      In some cases, there are a lot of request types created in a single Service Desk, and then if I want to use the same request types in another project, I will have to create them by hand.

      If the Admin was able to copy them to the other project, it would save some time.

            [JSDCLOUD-1317] Ability to copy request types to another Service Management project.

            Patenaude, Travis added a comment -

            This would be incredibly helpful.  If nothing else, export to a template and import into the other projects.

            Patenaude, Travis added a comment - This would be incredibly helpful.  If nothing else, export to a template and import into the other projects.

            Egils Sverns added a comment - - edited

            What about this year? Or the situation is still stable (not moved even a step)? 

            We wanted to create a template in Service desk so that our customers could fill it in a way and then forward the issue to another project to QA/Development. How hard can it be, right? Well... Issue templates are not supported in Service desk, Forms - are, looks kinda good, but then there's this current issue created back in 2014  

            We don't want to create a Description2 field with this template and then create automations to copy it's content+hide/show fields etc... especially when looks at the bills from Atlassian

             

            Egils Sverns added a comment - - edited What about this year? Or the situation is still stable (not moved even a step)?  We wanted to create a template in Service desk so that our customers could fill it in a way and then forward the issue to another project to QA/Development. How hard can it be, right? Well... Issue templates are not supported in Service desk, Forms - are, looks kinda good, but then there's this current issue created back in 2014   We don't want to create a Description2 field with this template and then create automations to copy it's content+hide/show fields etc... especially when looks at the bills from Atlassian  

            Felix Malinis added a comment -

            I created a bunch of forms in a test project (on a production instance), and I was able to copy those forms to the main project. Nice! Then I thought, there shouldn't be any problem copying the underlying request type, right? No! Argh! Where's the "copy to project" function that the forms have?! Can't find it. Google, google, google. Nothing. I come across this feature request. Wtf!

            Felix Malinis added a comment - I created a bunch of forms in a test project (on a production instance), and I was able to copy those forms to the main project. Nice! Then I thought, there shouldn't be any problem copying the underlying request type, right? No! Argh! Where's the "copy to project" function that the forms have?! Can't find it. Google, google, google. Nothing. I come across this feature request. Wtf!

            Konstantinos Sotiriou added a comment -

            Very useful.
            +1

            Konstantinos Sotiriou added a comment - Very useful. +1

            John Wilson added a comment -

            Our team needs this too. We've created several JSMs with similar purposes and want to merge them. Recreating each request type and associated form is unnecessary work.

            John Wilson added a comment - Our team needs this too. We've created several JSMs with similar purposes and want to merge them. Recreating each request type and associated form is unnecessary work.

            Patricia Limbu added a comment -

            Need this. 

            Patricia Limbu added a comment - Need this. 

            Josh Weiss added a comment -

            +1

            This is insane that this is still not a feature added to the product. Please look into this very basic ask. 

            Josh Weiss added a comment - +1 This is insane that this is still not a feature added to the product. Please look into this very basic ask. 

            svieville added a comment -

            +1

            svieville added a comment - +1

            Simon Herd (Inactive) added a comment -
            Update 15 May 2023

            Please be aware that we have not scheduled any development work on this issue through to the end of the fiscal year 2024 (June).

            However, your input remains incredibly valuable to us. We encourage you to keep voting and providing feedback. Every vote and piece of feedback informs our future priorities and helps us understand your needs better.

            Thank you for your understanding and your continued support.

            Regards,
            Simon
            JSM - Principal Product Manager

            Simon Herd (Inactive) added a comment - Update 15 May 2023 Please be aware that we have not scheduled any development work on this issue through to the end of the fiscal year 2024 (June). However, your input remains incredibly valuable to us. We encourage you to keep voting and providing feedback. Every vote and piece of feedback informs our future priorities and helps us understand your needs better. Thank you for your understanding and your continued support. Regards, Simon JSM - Principal Product Manager

            Rajendra Prabhu Sivasamy added a comment -

            Any update on this please? This feature is required to resolve our use case. 

            Rajendra Prabhu Sivasamy added a comment - Any update on this please? This feature is required to resolve our use case. 

              96677a1d9b4c Sam Knight
              psouza Pedro Souza
              Votes:
              362 Vote for this issue
              Watchers:
              205 Start watching this issue

                Created:
                Updated: