Uploaded image for project: 'Jira Service Management Cloud'
  1. Jira Service Management Cloud
  2. JSDCLOUD-6339

Update Request Type automatically when issue type is moved

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Duplicate
    • Issue View
    • None
    • 1
    • 2

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Request type is always No match if the issue type has changed by moving the ticket 

      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

            [JSDCLOUD-6339] Update Request Type automatically when issue type is moved

            Paulo Junior (Inactive) added a comment -

            Duplicates JSDCLOUD-1835

            Paulo Junior (Inactive) added a comment - Duplicates JSDCLOUD-1835

            Jehan Gonsalkorale added a comment -

            Hi all,

            Thanks for your feedback here. This is part of an initiative we have planned for the future but we are still prioritising it against competing initiatives. I'll provide an update once we have a timeline, this is something we care about and hope to improve soon.

            Sorry again that we can't provide any improvements here sooner, we are watching this space and will provide an update soon.

            Cheers,

            Jehan

            Jehan Gonsalkorale added a comment - Hi all, Thanks for your feedback here. This is part of an initiative we have planned for the future but we are still prioritising it against competing initiatives. I'll provide an update once we have a timeline, this is something we care about and hope to improve soon. Sorry again that we can't provide any improvements here sooner, we are watching this space and will provide an update soon. Cheers, Jehan

            Zhi-Xian Goh added a comment -

            Hi,

             

             This issue relates to  JSDCLOUD-8405

             For the automation role, why is there no trigger role when an issue is moved, but only when created?

            Zhi-Xian Goh added a comment - Hi,    This issue relates to   JSDCLOUD-8405  For the automation role, why is there no trigger role when an issue is moved, but only when created?

            Jehan Gonsalkorale added a comment -

            Thanks for flagging this issue and for all the comments, we are onto it. We'll review it and come back to you all once we have a plan.

            Jehan Gonsalkorale added a comment - Thanks for flagging this issue and for all the comments, we are onto it. We'll review it and come back to you all once we have a plan.

            Aymen Ben Tanfous added a comment -

            This would impact our business as we're constantly moving tickets through project on a daily basis.

            Please consider implementing this.

            Aymen Ben Tanfous added a comment - This would impact our business as we're constantly moving tickets through project on a daily basis. Please consider implementing this.

              rcrossman@atlassian.com Rachel Crossman (Inactive)
              hchukwu hylz (Inactive)
              Votes:
              8 Vote for this issue
              Watchers:
              21 Start watching this issue

                Created:
                Updated:
                Resolved: