Login
Contents x
Jira Assets Platform - Add Assets
  • 23 Mar 2023
  • 3 Minutes to read
  • Print
  • Dark
    Light
  • PDF
Contents

Jira Assets Platform - Add Assets

  • Updated on 23 Mar 2023
  • 3 Minutes to read
  • Print
  • Dark
    Light
  • PDF

Jira Assets Platform - Add Assets creates a new asset or updates an existing asset in Jira Assets Platform for each of the assets that are the results of the saved query supplied as a trigger (or devices that were selected in the asset table).

NOTE

Updating an asset will overwrite its properties with the properties defined in the request object from Axonius.

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 Axonious. You can change the name according to your needs.
  • Add description (optional) - 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.
  • Action name - The name of the Main action. A default value is added by Axonious. You can change the name according to your needs.
  • Configure Action Conditions - Toggle on to enter a condition statement. See Configuring Enforcement Action Conditions to learn more about condition statement syntax.

Connection Settings

  1. Jira Domain (required) - The hostname or IP address of the Atlassian Jira Assets Platform server.
  2. User Name and API Token (required) - The credentials for a user account that has the Required Permissions to read, add and to update assets.
  3. Verify SSL (required, default: True) - Verify the SSL certificate offered by the host supplied in Jira domain. For more details, see SSL Trust & CA Settings.
    • If enabled, the SSL certificate offered by the host will be verified against the CA database inside of Axonius. If it fails validation, the connection will fail with an error.
    • If disabled, the SSL certificate offered by the host will not be verified against the CA database inside of Axonius.
  4. HTTPS proxy (optional, default: empty) - A proxy to use when connecting to Jira domain.
    • If supplied, Axonius will utilize the proxy when connecting to the host defined for this connection.
    • If not supplied, Axonius will connect directly to the host defined for this connection.

Action Settings

  1. Asset type appKey and Asset type originId (required, default: AxoniusEC | axonius-enforcement) - Specify the appKey and the originId of an Asset Type you have created on your JIRA Assets Platform project.
  2. Assignee account ID (optional, default: empty) - Specify the Atlassian account id for the assignee.
    • If supplied, the new/updated asset will be assigned to the specified account.
    • If not supplied and Assignee email is not supplied, the new/updated asset will not be assigned.
  3. Assignee email (optional, default: empty) - Specify the email address for the assignee. The email must be associated with a valid Atlassian account id.
    • If supplied and there is an account id associated with this email address, the new/updated asset will be assigned to the specified account.
    • If not supplied, or if supplied and there is no account id associated with this email address, the new/updated asset will not be assigned.
NOTE

If both Assignee account ID and Assignee email are supplied, the action will fail.

APIs

Axonius uses the Atlassian Jira Asset Platform - Create or Update Asset API.

Required Permissions

The value supplied in User Name and in API Key must have read, add and update access to devices.

To integrate Axonius with Jira, you need to do the following :

  1. Create a user in Atlassian with access to Jira. The user should be part of the most basic group which is jira-software-users.

    image.png

  2. Log in to Jira using the created user and generate an API token.
    For cloud based Atlassian sites, use the following URL to generate an API token: https://id.atlassian.com/manage/api-tokens#

    image.png

For more details about other Enforcement Actions available, see Action Library.

What's Next
Change password!
Changing your password will log you out immediately. Use the new password to log back in.
Change profile
Success!
First name must have atleast 2 characters. Numbers and special characters are not allowed.
Last name must have atleast 1 characters. Numbers and special characters are not allowed.
Enter a valid email
Enter a valid password
Your profile has been successfully updated.
Logout