Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-4176

As a user, for service desk tickets, I want JIRA to prompt users to set request type when performing a move operation to change Issue Type

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Low Engagement
    • None
    • None
    • None
    • 3
    • 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.

      Problem Definition

      You can change Issue Types in JIRA using the Move function in the issue screen. When you use this function to move Service Desk issues, then the request type is lost when you change the Issue Type in the move.

      The workaround would be that to set the request type right after the move in the issue view by editing the request type field inline. However, this is not ideal as if forgotten or not done, then the issue is not viewable via the customer portal and so the issue could potentially be stuck waiting for customer but the customer has no visibility on it.

      Suggested Solution

      Include in the JIRA Issue Type move functionality the ability to specify the request type in the move function itself for Service Desk tickets so that the issue will have a request type as soon as the move is complete.

          Form Name

            [JSDSERVER-4176] As a user, for service desk tickets, I want JIRA to prompt users to set request type when performing a move operation to change Issue Type

            Charlie Marriott added a comment -
            Atlassian Update – 1 March 2021

            Hi,

            Thank you for raising and watching this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request.

            This is an automated update triggered by low engagement with this suggestion (number of votes, number of watchers).

            We hope you will appreciate our candid communication and our attempts to become more transparent about our priorities. You can read more about our approach to highly voted suggestions here, and how we prioritise what to implement here.

            To learn more about our recent investments in Jira Service Management and Data Center, please check our public roadmap and our two dashboards containing recently resolved issues, and current work and future plans.

            Regards,

            Jira Service Management, Server & Data Center

            Charlie Marriott added a comment - Atlassian Update – 1 March 2021 Hi, Thank you for raising and watching this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request. This is an automated update triggered by low engagement with this suggestion (number of votes, number of watchers). We hope you will appreciate our candid communication and our attempts to become more transparent about our priorities. You can read more about our approach to highly voted suggestions here , and how we prioritise what to implement here . To learn more about our recent investments in Jira Service Management and Data Center, please check our public roadmap and our two dashboards containing recently resolved issues , and current work and future plans . Regards, Jira Service Management, Server & Data Center

              Unassigned Unassigned
              mriza Mohamed Riza (Inactive)
              Votes:
              2 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: