Jira Software - Delete User
  • 24 Jun 2024
  • 2 Minutes to read
  • Dark
  • PDF

Jira Software - Delete User

  • Dark
  • PDF

Article summary

Jira Software - Delete User deletes a user in Atlassian (formerly Jira Software) for each asset that matches the parameters of the selected saved query, and the other Enforcement Action settings or the assets selected on the relevant asset page.

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.
  • 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 Atlassian (formerly Jira Software) adapter - Select this option to use the Atlassian 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.

Required Fields

These fields are required to run the Enforcement Action.

Additional Fields

These fields are optional.

Connection Parameters

If Use stored credentials from the Atlassian (formerly Jira Software) adapter is disabled, these fields are required:

  • Domain - The full URL of the Jira server.
  • User Name - The user name for a user account that has the Required Permissions to perform this Enforcement Action. Use only when accessing with the old API.
  • API Token - The API token to use when using the Jira API.
  • 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.

  • Jira API Version (default: V3) - Select your Jira API version.
  • Atlassian Admin API - Organization ID and Atlassian Admin API - API key - The organization ID and an organization API key generated for fetching SaaS data. Needed for fetching organizational data.
  • Password - The password for the Atlassian user account. Needed for fetching Settings from Atlassian.
  • 2FA Secret Key - If you access Atlassian through an SSO solution that requires two-factor authentication, and you want to fetch Settings from Atlassian, you will need to generate a secret key in that solution and paste it here. See instructions for performing this action in Okta.
  • Gateway Name - Select the gateway through which to connect to perform the action.


Axonius uses the Jira Cloud Platform REST API.


The credentials used to connect to Atlassian must have the permissions needed to delete users in Atlassian.

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

Was this article helpful?

Changing your password will log you out immediately. Use the new password to log back in.
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.