Jira Cloud Actions

Actions for Jira Cloud Platform #

• Create Jira Issue. Creates a ticket in Jira. For each record that matches the base query, the output fields are attached to the Jira ticket.

• Creates a Jira Asset. Creates a Jira asset in Jira Service Management.

Use Cases #

Below are the possible use cases for the Create Jira Issue action:

• Create a Jira ticket for each department that includes non-standard or non-compliant user names and assign the ticket to the department manager.

• Create a Jira ticket for each asset owner whose assets require patching or updating.

Below are the possible use cases for the Create Jira Asset action:

• Create an asset record that includes all asset information ingested and enhanced by Lucidum.

Prerequisites #

A Jira account that has global Jira administrators permission.

For details, see https://confluence.atlassian.com/adminjiraserver/managing-global-permissions-938847142.html

Workflows #

• Creating a new Configuration and a new Action
• Cloning an Existing Action
• Creating a new Action from the Location Results page
• Editing a Configuration
• Editing an Action
• Viewing Information about an Action

Jira Cloud Platform Configuration #

• Configuration Name. Identifier for the Configuration. This name will appear in the Lucidum Action Center.

• User Name . User name for a Jira account that has global Jira administrators permission.

  NOTE: This user must have global Jira administrators permission. For details, see https://confluence.atlassian.com/adminjiraserver/managing-global-permissions-938847142.html

  NOTE: If your organization requires more granular permissions, please contact your Lucidum Customer Success representative to help you with the required Jira permission.

• API Token. An API Token associated with the user account specified in User Name.

  NOTE: Jira provides both an API Key and an API Token. Lucidum uses only the API Token.

• URL. The base URL for the Jira Cloud API.

• Workspace ID. For Create Jira Asset action only. You can enter the Jira Workspace ID or enter “Default” and Lucidum will populate the field with the first Jira Workspace ID it finds.

Create or Edit an Action #

To create an action for Jira Cloud:

1. In the Create a New Action page, in the General step, enter:

   

   • Action Type. Select an action from the pulldown options. Choices are:

     • Create Jira Ticket. Creates a Jira ticket and attaches the output to the ticket.

     • Create Jira Asset. Creates a Jira asset in Jira Service Management.

   • Configuration Name. Select an action configuration from the pulldown options.

   • Action Name. Identifier for the action. This name will appear in the Lucidum Action Center.

   • Description. Description of the action.

2. Click the Next (>) icon.

3. In the Filters page, click Configure Filters.

   

4. The Build a Query page appears.

   

5. In the Build a Query page, you define the query for the assets or users that the action will act upon.

6. Click Next.

7. In the Build a Current Query page, enter the fields, operators, and values for the query. For existing actions, the query is already loaded in this page.

   
8. For details on creating and editing queries in Lucidum, see the section on Building Queries.

   NOTE: To optimize performance, the default time range is Current. If you need to access historical data, contact Lucidum Custom Success for help on using historical data without affecting performance.

9. Click the Apply (page and pencil) icon.

10. Click the Next (>) icon.

11. In the Schedule step, enter:

    =

    • Schedule Type. Define the schedule for the action. Choices are:

      • Recurrence. Specify a frequency for the recurring schedule.

      • After Data Ingestion. The action is executed after data ingestion, which happens at least once every 24 hours and can also be triggered manually.

    • Do not trigger the action unless. Specify the number of results from Filters as a prerequisite for executing the action.

12. Click the Next (>) icon.

13. The Details step differs depending on the action you choose in the General page.

14. If you choose Create a Jira Ticket in the Action Type field in the General page, the following fields appear in the Details page:

    

    • Output Fields. For the records selected with the Filters field, specify the columns to display. When creating or editing the query, you can select these fields in the Query Results page > Edit Column button.

    • Project Name. Name of the Jira project where you want to create the new issue.

    • Issue Type. Jira issue type for the new issue. For example, epic, story, task, bug.

    • Assignee. Account ID of the Jira user to assign the issue to.

      • To find the account ID, in Jira click on People menu. Select the user whose account ID you want to use. In the URL, the account ID is the string after “/” and before “/?ref”. In the example below, the account ID is the string that starts with “987dda”:

        https://acme.atlassian.net/jira/people/987dda88551f476a04685be6?ref=jira&src=peopleMenu/p>

    • Issue Subject. Description of the issue that will appear in the Summary field.

    • Issue Description. Description of the issue. The field includes a default Jinja template that you can edit. For details on Jinja, see https://jinja.palletsprojects.com/en/3.1.x/templates/.

    •  Attach output file. If enabled, Lucidum will attach the query results as a CSV file to the new Jira issue.

    • Update previously created issue. Specify whether you want to update the issue created with a previous execution of this action. If not select, the action will create a new Jira issue.

15. If you choose Create a Jira Asset in the Action Type field in the General page, the following fields appear in the Details page:

    

    • Output Fields. For the records selected with the Filters field, specify the columns to display. When creating or editing the query, you can select these fields in the Query Results page > Edit Column button.

    • Jira Asset Object Type ID. Numeric ID for the object type in Jira Service Management. The asset will be a member of the specified object.

    • Jira Asset Object Text Attribute ID Mappings. Mappings for a list of Lucidum field names to Jira attributes. Syntax is:

      • [Lucidum Field Name]->[Jira Attribute ID]

For example:

Lucidum Asset Name->26

maps the value of “Lucidum Asset Name” to the Jira attribute with an ID of “26”

• • Dedupe Previous Jobs. In this field, you specify whether you want duplicates of asset IDs (if your query is for assets) or user IDs (if your query is for users). You can specify integers starting at 0 (zero).

    • If you specify “0” (zero), Lucidum includes all the records from the query in each delivery to Jira.

    • If you specify “1” (one), Lucidum examines the previous payload and excludes records for asset IDs or user IDs that were sent in the delivery to Jira.

    • If you specify “2” (two), Lucidum examines the last two payloads and excludes records for asset IDs or user IDs that were sent in the previous two deliveries to Jira.

16. Click Save.