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

Update Request Type automatically when issue is moved to different project or different workflow

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

      Request type is always No match if

      • the issue has been created directly in JIRA
      • the issue type has changed by editing this field (same workflow)
      • the issue type has changed by moving the ticket (same project but different workflows)
      • the ticket has been moved between different Service Desk projects

      Suggested solution

      Automatically update the request type corresponding to its issue type

      Workaround

      If the Move operation involves status changing, you can use the workaround below:

      1. The Request type Heartware problem is associated with the Issue type Problem.
      2. Create an automation rule like the one below and include all existing request types and issue types. Whenever the status of any issue changed, if the issue type is not matching with the request type, set it accordingly.

        1. reqType.png
          reqType.png
          2 kB
        2. rule.png
          rule.png
          11 kB

          Form Name

            [JSDSERVER-5044] Update Request Type automatically when issue is moved to different project or different workflow

            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 ]

            Charlie Marriott added a comment -
            Atlassian Update – 5 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,

            Charlie

            Jira Service Management, Server & Data Center

            Charlie Marriott added a comment - Atlassian Update – 5 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, Charlie Jira Service Management, Server & Data Center
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3012902 ] New: JAC Suggestion Workflow 3 [ 3651208 ]
            Eduardo Santos made changes -
            Description Original: h3. Problem definition
            Request type is always _No match_ if
            * the issue has been created directly in JIRA
            * the issue type has changed by editing this field (same workflow)
            * the issue type has changed by moving the ticket (same project but different workflows)
            * the ticket has been moved between different Service Desk projects

            h3. Suggested solution
            Automatically update the request type corresponding to its issue type

            h3. Workaround
            If the Move operation involves status changing, you can use the workaround below:
            # The Request type _Heartware problem_ is associated with the Issue type _Problem_.
             !reqType.png|thumbnail!
            # Create an automation rule like the one below and include all existing request types and issue types. Whenever the status of any issue changed, if the issue type is not matching with the request type, set it accordingly.
             !rule.png|thumbnail!             		New: {panel:bgColor=#e7f4fa}
              *NOTE:* This suggestion is for *JIRA Service Desk Server*. Using *JIRA Service Desk Cloud*? [See the corresponding suggestion|https://jira.atlassian.com/browse/JSDCLOUD-8405].
              {panel}
            h3. Problem definition
            Request type is always _No match_ if
            * the issue has been created directly in JIRA
            * the issue type has changed by editing this field (same workflow)
            * the issue type has changed by moving the ticket (same project but different workflows)
            * the ticket has been moved between different Service Desk projects

            h3. Suggested solution
            Automatically update the request type corresponding to its issue type

            h3. Workaround
            If the Move operation involves status changing, you can use the workaround below:
            # The Request type _Heartware problem_ is associated with the Issue type _Problem_.
             !reqType.png|thumbnail!
            # Create an automation rule like the one below and include all existing request types and issue types. Whenever the status of any issue changed, if the issue type is not matching with the request type, set it accordingly.
             !rule.png|thumbnail!
            SET Analytics Bot made changes -
            Support reference count Original: 2 New: 3
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2665061 ] New: JAC Suggestion Workflow [ 3012902 ]

            Daniel added a comment -

            use bulk change Jira !

            Daniel added a comment - use bulk change Jira !
            SET Analytics Bot made changes -
            Support reference count New: 2
            Owen made changes -
            Workflow Original: JSD Suggestion Workflow - TEMP [ 2324785 ] New: Confluence Workflow - Public Facing v4 [ 2665061 ]
            Status Original: Open [ 1 ] New: Gathering Interest [ 11772 ]

              Unassigned Unassigned
              michin Michelle Chin
              Votes:
              6 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated:
                Resolved: