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

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

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

            Stephan Vos added a comment - - edited

            Still  happening.... Moving Issue type in the same project.

            Target Issue only has one Customer Request Type linked to it so should be able to automatically match it.

            This should be easy to fix...

            Stephan Vos added a comment - - edited Still  happening.... Moving Issue type in the same project. Target Issue only has one Customer Request Type linked to it so should be able to automatically match it. This should be easy to fix...

            Thomas Heidenreich (//S) added a comment -

            The problem also exists when changing the Issue Type within the same project!

            Thomas Heidenreich (//S) added a comment - The problem also exists when changing the Issue Type within the same project!

            Meg Holbrook added a comment -

            Any clues as to why this isn't available in the API? Even if Atlassian didn't want to update the stock automation options, plenty of us are using third-party automation tools and scripts that could make the adjustment. 

            Currently I have no way to automate this update, which causes email notifications to be nonexistent. Very problematic and a manual step that could be avoided. 

            Meg Holbrook added a comment - Any clues as to why this isn't available in the API? Even if Atlassian didn't want to update the stock automation options, plenty of us are using third-party automation tools and scripts that could make the adjustment.  Currently I have no way to automate this update, which causes email notifications to be nonexistent. Very problematic and a manual step that could be avoided. 

            Michael Hönes added a comment -

            +1, this issue is a big source for user errors

            Michael Hönes added a comment - +1, this issue is a big source for user errors

            David LaVoie added a comment -

            This would be a huge time saver for us, since we have to manually select these. If we don't, it doesn't send emails to Request Participants, a custom field we have set up that seems to have come with Jira.

            David LaVoie added a comment - This would be a huge time saver for us, since we have to manually select these. If we don't, it doesn't send emails to Request Participants, a custom field we have set up that seems to have come with Jira.

            Shane Jorgenson added a comment -

            This is something that's plagued me for years now in JIRA. I have the same request types in both projects and moving between projects causes "No Match" to show up.

            Shane Jorgenson added a comment - This is something that's plagued me for years now in JIRA. I have the same request types in both projects and moving between projects causes "No Match" to show up.

            Sue Beck added a comment -

            Only an Atlassian agent can do that I believe...

            Sue Beck added a comment - Only an Atlassian agent can do that I believe...

            nprasad added a comment -

            Is there a way to change this ticket to a Bug ticket instead of a suggestion?

            nprasad added a comment - Is there a way to change this ticket to a Bug ticket instead of a suggestion?

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

                Created:
                Updated:
                Resolved: