Skip to main content
Skip table of contents

Jira Cloud Actions

Actions for Jira Cloud Platform

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

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.

Prerequisites

A Jira account that has permissions to create tickets.

Workflows

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 can read and create issues on Jira.

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

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

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.

      • 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 Configure Filters for Action page appears.

  5. In the Configure Filters for Action page, you define the query for the assets or users that the action will act upon. For existing actions, the query is already loaded in this page.

  6. For details on creating and editing queries in Lucidum, 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.

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

  8. Click the Next (>) icon.

  9. 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.

  10. Click the Next (>) icon.

  11. In the Details step, enter the following:

    • 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.

    • Original Estimate. Number of weeks, days, and hours to complete the work in the issue. An example of the format for this field is: 3w 4d 12h. This means 3 weeks, 4 days, and 12 hours.

    • Remaining Estimate. Number of weeks, days, and hours left to complete the work in the issue. An example of the format for this field is: 3w 4d 12h. This means 3 weeks, 4 days, and 12 hours.

    • Assignee. Jira user to assign the issue to.

    • Issue Subject. Description of the issue that will appear in the Summar 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.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.