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

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

    XMLWordPrintable

Details

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

    Description

      NOTE: This suggestion is for JIRA Service Desk Cloud. Using JIRA Service Desk Server? 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. 

      Attachments

        Issue Links

          Activity

            People

              a620038e6229 Jehan Gonsalkorale
              esantos@atlassian.com Eduardo Santos (Inactive)
              Votes:
              21 Vote for this issue
              Watchers:
              24 Start watching this issue

              Dates

                Created:
                Updated: