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

Option to select the Request Type on Create Linked Issue screen for JSM Projects

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • Issue View
    • None
    • 46
    • 11
    • 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.

      Issue Summary

      Currently, when creating a Linked Issue for a JSM Project, we only have the option to select the Issue Type, not the Request Type for the linked ticket. Since we cannot Create a Linked Issue Screen as per JSDCLOUD-3917, we should have a default option to enter the values for the Request Type.

      Steps to Reproduce

      1. Open an existing issue from any JSM project and click on the Link Issue button > + Create linked issue;


      2. On the Create linked issue screen, notice that we only see the option to select the Issue Type, not the Request type.

      Expected Results

      Since we are creating a linked issue from an existing JSM ticket, we should have the option to select the Request Type of the ticket.

      Actual Results

      On the Create linked issue screen, we can only select the Issue Type for the ticket.

      Workaround

      The workaround is to create an Automation Rule to set the Request Type for any ticket which has an empty value for this field.

          Form Name

            [JSDCLOUD-15179] Option to select the Request Type on Create Linked Issue screen for JSM Projects

            Would someone please be assigned to this Work Item and let us know the status and about how many requests you need for this so it's reviewed for the roadmap? Thanks much.

            Susan Waldrip added a comment - Would someone please be assigned to this Work Item and let us know the status and about how many requests you need for this so it's reviewed for the roadmap? Thanks much.

            It would be very helpful if the requirement is implemented

            JiCo-ADMIN|Steffen Schmerler added a comment - It would be very helpful if the requirement is implemented

            Sue Lund added a comment -

            This is something that should be fixed.  Not being able to select the request type while creating a ticket means essential fields are missing.

            Sue Lund added a comment - This is something that should be fixed.  Not being able to select the request type while creating a ticket means essential fields are missing.

            Lothar added a comment -

            Hi, for our IT service desk project, Request Type is a condition in the creation step of our workflow, because the request type is essential for the workflow and for reporting, issue classification, filtering and so on.

            Why is a field so essential, left out of a Create Issue-form?

            Please consider for near future implementation.

            Lothar added a comment - Hi, for our IT service desk project, Request Type is a condition in the creation step of our workflow, because the request type is essential for the workflow and for reporting, issue classification, filtering and so on. Why is a field so essential, left out of a Create Issue-form? Please consider for near future implementation.

            Hello there,

             

            I noticed that at the start of this year the Crated Linked Issue screen had the optin to use Request Types but then it went away just a few days later. This is a major oversight in functionality and make it much more difficult for our teams to collaborate seamlessly.

             

            Is there possibly any update to this?

            Tyler Elliott added a comment - Hello there,   I noticed that at the start of this year the Crated Linked Issue screen had the optin to use Request Types but then it went away just a few days later. This is a major oversight in functionality and make it much more difficult for our teams to collaborate seamlessly.   Is there possibly any update to this?

            The Create linked issue screen does NOT show the Request type field. (JSM Cloud Premium) What gives?

            Paul Heath Armengol added a comment - The Create linked issue screen does NOT show the Request type field. (JSM Cloud Premium) What gives?

            We recently released an update where the Create linked issue screen starts surfacing the Request type field. This was tracked in JSDCLOUD-3917.

            Thank you,
            Arbaaz Gowher
            Product Manager, Jira Cloud

            Arbaaz Gowher (Inactive) added a comment - We recently released an update where the Create linked issue screen starts surfacing the Request type field. This was tracked in JSDCLOUD-3917 . Thank you, Arbaaz Gowher Product Manager, Jira Cloud

            creating a linked ticket should be exactly like using the "create button". Make it happen!!!

            thanks

            andrew r meyers added a comment - creating a linked ticket should be exactly like using the "create button". Make it happen!!! thanks

            The Customer Request Type is a fundamental component to an Issue. Without it, public comments never reach the Reporter and the Reporter/Customer never sees the open Issue in their request portal. Having users be prompted to insert this value is needed, especially in projects that have a delineation between request types. Alternatively, I will accept Jira automatically inserting the Customer Request Type value of the parent Issue if it is easier to implement.

            Peter Walker added a comment - The Customer Request Type is a fundamental component to an Issue. Without it, public comments never reach the Reporter and the Reporter/Customer never sees the open Issue in their request portal. Having users be prompted to insert this value is needed, especially in projects that have a delineation between request types. Alternatively, I will accept Jira automatically inserting the Customer Request Type value of the parent Issue if it is easier to implement.

              Unassigned Unassigned
              rsilva@atlassian.com Rodrigo Silva
              Votes:
              52 Vote for this issue
              Watchers:
              31 Start watching this issue

                Created:
                Updated: