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

            Alex Cooksey made changes -
            Resolution Original: Won't Do [ 10000 ] New: Low Engagement [ 10300 ]
            Status Original: Closed [ 6 ] New: Closed [ 6 ]
            Charlie Marriott made changes -
            Resolution New: Won't Do [ 10000 ]
            Status Original: Gathering Interest [ 11772 ] New: Closed [ 6 ]
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3011253 ] New: JAC Suggestion Workflow 3 [ 3648673 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2663864 ] New: JAC Suggestion Workflow [ 3011253 ]
            SET Analytics Bot made changes -
            Support reference count New: 3
            Owen made changes -
            Workflow Original: JSD Suggestion Workflow - TEMP [ 2322452 ] New: Confluence Workflow - Public Facing v4 [ 2663864 ]
            Status Original: Open [ 1 ] New: Gathering Interest [ 11772 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Suggestion Workflow [ 2053910 ] New: JSD Suggestion Workflow - TEMP [ 2322452 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Suggestion Workflow - TEMP [ 2049170 ] New: JSD Suggestion Workflow [ 2053910 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Suggestion Workflow [ 1589584 ] New: JSD Suggestion Workflow - TEMP [ 2049170 ]
            jonah (Inactive) made changes -
            Description Original: h3. 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.
            h3. 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.             		New: {panel:bgColor=#e7f4fa}
              *NOTE:* This suggestion is for *JIRA Service Desk Server*. Using *JIRA Service Desk Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JSDCLOUD-4176].
              {panel}

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

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

                Created:
                Updated:
                Resolved: