.png?sv=2022-11-02&ss=b&srt=o&spr=https&st=2024-04-29T20%3A58%3A44Z&se=2024-04-29T21%3A08%3A44Z&sp=r&sig=XLtrWJlp%2FDqSnn1N6%2BjSWJpPnKqRYZeV%2FO8L4VcwGxs%3D){kind=logo}
Jira Service Management - Update Tickets
- 30 Jan 2024
- 3 Minutes to read
- Print
- DarkLight
- PDF
Jira Service Management - Update Tickets
- Updated on 30 Jan 2024
- 3 Minutes to read
- Print
- DarkLight
- PDF
Article Summary
Share feedback
Thanks for sharing your feedback!
Jira Service Management - Update Tickets updates the relevant tickets for assets matching the Enforcement Set query. For example, if the action is triggered on asset=Users, the ticket updates tickets linked to each user.
See Creating Enforcement Sets to learn more about adding Enforcement Actions to Enforcement Sets.
General Settings
- Enforcement Set name (required) - The name of the Enforcement Set. A default value is added by Axonius. You can change the name according to your needs.
- Add description - Click to add a description of the Enforcement Set. It is recommended to describe what the Enforcement Set does.
- Run action on assets matching following query (required) - Select an asset category and a query. The Enforcement Action will be run on the assets that match the query parameters.
- A query only returns results for the asset type it was created for.
- Not all asset categories are supported for all Enforcement Actions.
- See Actions supported for Activity Logs, Adapters Fetch History, and Asset Investigation modules.
- See Actions supported for Vulnerabilities.
- See Actions supported for Software.
- Action name (required) - The name of the Main action. A default value is added by Axonius. You can change the name according to your needs.
- Configure Dynamic Values - Toggle on to enter a Dynamic Value statement. See Creating Enforcement Action Dynamic Value Statements to learn more about Dynamic Value statement syntax.
Use stored credentials from Jira Service Management (Service Desk) adapter - Select this option to use the Jira Service Management connected adapter credentials.
- When you select this option, the Select Adapter Connection drop-down is available, and you can choose which adapter connection to use for this Enforcement Action.
Note:To use this option, you must successfully configure a Jira Service Management (Service Desk) adapter connection.Required Fields
These fields must be configured to run the Enforcement Set.
- {{snippet.Instance Name}}
Additional Fields
- Additional fields (json format) - Specify additional fields to be added as part of the incident as key/value pairs in a JSON format.
For example:
{"field1": "value1", "field2": "value2"}
- Status of the Ticket- Status of the Jira ticket.
- Ticket Assignee - The Jira user assigned to the ticket.
- Ticket CommentsComments to be added to the ticket.
- Select Which Related Tickets To Update - Select one of the options or enter the ID of a specific ticket to update and click create new.
- All Related Tickets - All tickets linked to the main asset.
- Last Created Ticket - The latest ticket linked to the main asset.
Map Axonius fields to adapter fields - Use the Field Mapping Wizard to map Axonius fields to fields in external systems. In this way you can transfer data found in Axonius into the external system as part of the configuration of relevant enforcement actions. The wizard shows you which fields exist on the Axonius system, allowing you to map them easily.
Note:For details, see Axonius to External Field Mapping.
Connection Parameters
If Use stored credentials from the Jira Service Management adapter is not enabled, these fields are required.
Host Name or IP Address -The hostname or IP address of the Jira Service Management server.
Jira Service Management API version - The Jira Service Management API number.
User Name and API Token - The credentials for a user account that has the permissions to read and write.
Verify SSL - Select whether to verify the SSL certificate of the server against the CA database inside of Axonius. For more details, see SSL Trust & CA Settings.
HTTPS Proxy - Connect the adapter to a proxy instead of directly connecting it to the domain.
HTTPS Proxy User Name - The user name to use when connecting to the server using the HTTPS Proxy.
HTTPS Proxy Password - The password to use when connecting to the server using the HTTPS Proxy.
Use Cloud API - Select this option to explicitly specify that the enforcement should use the Cloud API instead of Jira Server API. When the user is using the cloud API the default host name or IP address should be https://api.atlassian.com. Even when left unselected, the action will attempt to use the cloud API if the domain specified is “api.atlassian.com”.
For more details about other Enforcement Actions available, see Action Library.
Was this article helpful?