Version: 3.6.0

Jira Software

Configuration

Follow these steps to configure Ticketing Integration with Jira Software. Ensure you have the following information ready:

info

Requirements:

Atlassian Space URL: Your atlassian cloud instance URL, e.g. https://yourcompany.atlassian.net
Jira Issue URL: The navigable link to a Jira issue
e.g. https://yourcompany.atlassian.net/browse/{remote_ticket_id}
Jira Issue Enumerators: Values for fields you want to map (e.g. status, urgency, impact). These values enable AME to sync events flexibly with Jira's internal representations. Obtain these values from your Jira administrator.
- For example, "New" = 10176, "In Progress" = 10174
Authentication Parameters: Consult your Jira administrator to create an API token for AME to authenticate with. Use it as the password in combination with the email address of the user the token was created for through basic authentication.

Make sure to map or template the field "summary" as it is required to create a Jira issue.

For an in-depth guide on using a ticketing integration, make sure to read the guide for ServiceNow as the concepts are the same. The only difference are the meta configurations that are specific to the remote system.

For Jira these are as follows:

Project Template: A Jinja2 template string (can be static) that resolves to the project key or ID in which the issue should be created. This is a required field.
Project Template Target: Either "Key" or "ID", depending on what the template resolves to.
Issue Type Template: A Jinja2 template string (can be static) that resolves to the issue type name or ID. This is a required field.
Issue Type Template Target: Either "Name" or "ID", depending on what the template resolves to.

info

Custom Fields with nested IDs: Some fields in Jira are custom fields and declare a nested ID structure. For example, the data structure for the field "priority" is:

"priority": {
    "self": "https://yourcompany.atlassian.net/rest/api/3/priority/4",
    "iconUrl": "https://yourcompany.atlassian.net/images/icons/priorities/low_new.svg",
    "name": "Low",
    "id": "4"
},

To work with fields like this, list them as priority in the "Custom Fields with nested IDs" input.

For more information, see:
Event Summary, Templates, Tenants

Configuration​

Configuration