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
          2 kB
          hylz
        2. rule.png
          11 kB
          hylz

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

              Created:
              Updated:
              Resolved: