Automatically set Customer Request Type When Issue is Moved or Created via Jira

Still need help?

The Atlassian Community is here for you.

Ask the community

Platform Notice: Cloud Only - This article only applies to Atlassian products on the cloud platform.


Below you can find a solution to the problems described in Requests not visible in the Jira Service Management Customer Portal using automation.


Each request type is based on an issue type and can only be selected for issues of the associated type. If the chosen request type isn't based on the current issue type, the automation rule will result in an error. To avoid errors, we'll create conditions to make sure that a valid request type is selected for every issue type used in the project.

  1. Go to your service project > Project settings > Automation > click on Create rule
  2. Select the trigger Multiple issue events and include the events "Issue Created", "Issue Moved", and "Issue Updated" (in order to cover all scenarios that cause the problem)
  3. Click on New condition and select the option If / else block
  4. Click on Add conditions and choose Issue fields condition > select 'Field: Issue Type' / 'Condition: equals' / 'Value: Bug' (for example)
  5. Click on New action > choose Edit request type > select a request type that is based on the Bug issue type > Save
  6. Click on Add else and repeat steps 4 and 5, selecting another issue type and choose a request type associated with it (you can add multiple 'Else-if' blocks according to the number of issue types used in your project)
  7. Give your rule a name and click on Turn it on.

Your rule should look like this:

DescriptionThis article details how to automatically set a Request Type when an issue is created through Jira.
Last modified on Sep 15, 2021

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.