- 19 May 2024
- 3 Minutes to read
- Print
- DarkLight
- PDF
Jira - Create Issue per Asset
- Updated on 19 May 2024
- 3 Minutes to read
- Print
- DarkLight
- PDF
This Enforcement Action has been deprecated from Axonius version 6.0.18. Use Jira Service Management - Create Ticket per Asset instead.
Jira - Create Issue per Asset creates an an issue in your Jira server for each entity retrieved from the saved query supplied as a trigger (or from the entities selected in the asset table) .
This is for Asset Management with Insight.
Details for all devices are included in the ticket message as well as the CSV.
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 - 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.
To create a single Jira issue for all relevant entities, use the Jira - Create Issue.
To use this action, you must enable the Use Jira setting and configure your Jira server. For more details, see Configuring Jira Settings.
Required Fields
These fields must be configured to run the Enforcement Set.
Project Key (required) - Specify or select the desired project in Jira where the issue will be created.
Issue type (required) - Specify or select the issue type for the created issue.
Summary (required) - Specify a summary for the created issue.
NOTEYou can replace text with params that can assist you in better informing in the Jira Issues.
The following params can be used:
{{HOSTNAME}}, {{USERNAME}}, {{FIRST_NAME}}, {{LABELS}}Description (required) - Specify a description for the created issue.
NOTEYou can replace text with params that can assist you in better informing in the Jira Issues.
The following params can be used:
{{HOSTNAME}}, {{USERNAME}}, {{FIRST_NAME}}, {{LABELS}}Instance Name - The Axonius node to use when connecting to the specified host. For more details, see Connecting Additional Axonius Nodes.
Additional Fields
These fields are optional.
Add full device content (required, default: False) - Add all the data on the specific entity to the ticket
Add device description - use the "Description" of the device in Axonius as the description of the ticket.
Multiple optional fields for the created issue (optional, default: empty)
- Assignee - A single user to assign the tickets to
- Labels - Comma separated labels that will be added to the tickets
- Components - Comma separated components that will be added to the ticketsNOTESince the valid values of the different parameters are customer specific, Axonius does not validate any of those parameters values. You must make sure inserted values are correct, otherwise, the request might fail.
Additional fields (optional, default: empty) - 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"}.
- If supplied, Axonius will add the specified fields and values to the created issue. If one of the specified fields is invalid, the request might fail.
- If not supplied, Axonius will not any additional fields to the created issue.
Axonius to Jira field mapping - Use this setting to map Axonius fields to the CMDB fields. The input should be key/value pairs in a JSON format.
For example: {axonius_field1
:jira_field1
, axonius_field2
:jira_field2
}
Alternative Jira Parameters
By default the system uses the Jira settings that are configured on the Global Configuration page. Use the Alternative parameters to set a different Jira server to override the default Jira Settings.
Set the following parameters:
- Alternative Jira domain
- Alternative User name
- Alternative API Token
- Alternative Verify SSL
- Alternative Use assignee name instead of ID - Refer to Jira Settings for explanations of these parameters.
For more details about other Enforcement Actions available, see Action Library.
For more details about other Enforcement Actions available, see Action Library.