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.


A Jira account that has permissions to create tickets.


To create an action in Lucidum, follow these steps:

  1. Choose Action Center from the left pane.

  2. In the Action Center, choose from the action types in the Channels pane.

  3. To create a configuration for the action, click the Manage Configuration button. A configuration provides the connection and authorization information to communicate with the external solution.

  4. Save the configuration.

  5. To create an action, click the Create a new action button. An action specifies the task to execute, the data to include in the action, and how frequently to execute the action.

  6. Save the action.

  7. Lucidum automatically executes the action at the time and recurrence you defined in the action.

You can apply an existing configuration to more than one action. If a configuration already exists, you might be able to re-use the existing configuration and might not need to create a new one.

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 a new action/View Action

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

  • Filters. For new actions, the Add Filter button leads to the New Query page, where you can query for the assets or users that the action will act upon. For existing actions, this field displays the query for this action. The Edit Filter button leads to the New Query page, with the current query already loaded for editing. For details on creating and editing queries in Lucidum, the section on Building Queries.

  • Schedule Settings. Define the schedule for the action. Choices are setting a Recurrence by date and time or 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.

  • Output Fields. The fields selected for the Filters. 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.

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