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

Allow For Selecting Customer Request Types When Moving Issues Between SD Projects

XMLWordPrintable

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

      Currently, when moving an issue to another Service Desk project, you only have the option to change the issue type. It would be nice if you had the option of choosing the customer request type from the project that you are moving the issue to

          Form Name

            [JSDSERVER-3613] Allow For Selecting Customer Request Types When Moving Issues Between SD Projects

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3012917 ] New: JAC Suggestion Workflow 3 [ 3645759 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Mandeep Singh made changes -
            Comment [ Prior to 3.7.0, the request type field would never show on the move issue workflow (across JSD projects). But that was fixed in 3.7.0.

            But, what still remains to be addressed is: when moving from a non-JSD project to a JSD project, it does not ask for the customer request type to be set. This will be taken up as a separate bug - tracked using JSDSERVER-6403. Marking this suggestion resolved.
            ]
            Mandeep Singh made changes -
            Resolution New: Fixed [ 1 ]
            Status Original: Gathering Interest [ 11772 ] New: Resolved [ 5 ]

            Mandeep Singh added a comment -

            Prior to 3.7.0, the request type field would never show on the move issue workflow (across JSD projects). But that was fixed in 3.7.0.

            But, what still remains to be addressed is: when moving from a non-JSD project to a JSD project, it does not ask for the customer request type to be set. This will be taken up as a separate bug - tracked using JSDSERVER-6403. Marking this suggestion resolved.

            Mandeep Singh added a comment - Prior to 3.7.0, the request type field would never show on the move issue workflow (across JSD projects). But that was fixed in 3.7.0. But, what still remains to be addressed is: when moving from a non-JSD project to a JSD project, it does not ask for the customer request type to be set. This will be taken up as a separate bug - tracked using JSDSERVER-6403 . Marking this suggestion resolved.
            Mandeep Singh made changes -
            Fix Version/s New: 3.7.0 [ 72395 ]

            Mandeep Singh added a comment -

            3613 is partially fixed and 6403 has been created to fix it completely. Linking both the issues.

            Mandeep Singh added a comment - 3613 is partially fixed and 6403 has been created to fix it completely. Linking both the issues.
            Mandeep Singh made changes -
            Link New: This issue was split into JSDSERVER-6403 [ JSDSERVER-6403 ]
            Mandeep Singh made changes -
            Link New: This issue has a derivative of JSDSERVER-6403 [ JSDSERVER-6403 ]
            SET Analytics Bot made changes -
            UIS Original: 171 New: 143
            SET Analytics Bot made changes -
            UIS Original: 168 New: 171

              Unassigned Unassigned
              jaguilar Javier Aguilar (Inactive)
              Votes:
              70 Vote for this issue
              Watchers:
              56 Start watching this issue

                Created:
                Updated:
                Resolved: