Set Ticket Priority Based on Asset Attributes
Scenario
When an ticket is opened in Jira Service Management, you want to set the Priority of the ticket based on the attached Asset’s attributes.
Note: This use case requires Jira Service Management and uses a custom Asset field. For more information on creating and configuring Assets in JSM, see this page.
Resolution
This requires that a custom field for an Asset has been added to your project; it can have any name and can represent any type of Asset, but it must be an Asset object to successfully use the steps as outlined. By accessing the Asset’s attributes, you can update the ticket’s priority when the ticket’s Asset meets specific critera; for example, if you have a networking device Asset with a Priority attribute set to ‘Critical’, any tickets created that have that Asset attached can automatically be assigned the highest priority.
Note: the steps below use an example Asset object with an attribute of Priority. You will need to modify the included script for your specific JSM setup.
Additionally, the script uses Jira Cloud’s Asset API to access the attribute values because these values are not accessible using the insightFieldValue custom Nunjucks filter. In order to access the attribute values through the Cloud API, you will need to provide your Atlassian username and an Access Token within the Nunjucks script.
You are viewing the documentation for Jira Cloud.
On This Page
Steps to Create
1. Add the Assets object custom field
Verify that your Jira project has a custom Assets object field, and that that field has been added to all necessary screens. Additionally, you will need to verify that it has been fully configured per the Atlassian instructions. If that custom field does not exist, create one and add it wherever is necessary for your processes; see this page for more information: https://support.atlassian.com/jira-service-management-cloud/docs/set-up-the-assets-object-field/ .
2. Add Set issue fields post-function
Log in to your Jira instance as an Administrator.
In the upper right corner of the window, click Settings ( ) and select Issues.
In the left-hand sidebar, click Workflows.
From the list of Workflows, click Actions ( ) for the appropriate workflow and select Edit.
Edit the transition:
When viewing the Workflow in Diagram view (Figure 1, right), select the Transition and click the Post Functions link. Click Add post function at the top of the list of existing post functions.
When viewing the Workflow in Text view, click the name of the Transition then select the Post Functions tab. Click Add post function at the top of the list of existing post functions.
Select Set issue fields (JMWE app) from the list of post-functions and click Add.
3. Configure the post-function
Set the following configurations (Figure 2, right):
Issue(s) to operate on - Set Target issue(s) to Current Issue.
Set fields
From the Add field(s) pulldown menu, select Priority. The Priority field will be added to the list of fields that will be updated by the post function.
For the Priority field’s configurations, set the Options as needed.
Also under the Priority field, use the following script for the Value:
{% set assetURL = issue | insightFieldValue( "customfield_xxxxx", true ) | first | field("links.self") %} {% set assetPriority = assetURL | callRest(options = { "auth": { "username": "your email address tied to your Atlassian account", "password": "your Atlassian API token value" } }) | field("attributes") | filter({"objectTypeAttributeId":"the object attribute ID"}) | field("objectAttributeValues") | first | field("value") %} {% if assetPriority == "Critical" %} Highest {% else %} Medium {% endif %}
Conditional execution - Set as needed.
Run As - Set as needed; it is recommended to leave the default Add-on user value unless required for specific reasons.
Delayed execution - Set as needed.
Click Add.
