You can integrate your Lumar account with Jira Cloud to create delivery tickets directly from Lumar’s Task Manager. This helps you move from issue discovery to delivery faster, with the option to include AI-generated ticket content for more detailed, developer-friendly handoffs.
Note: Due to Jira API restrictions, this integration supports Jira Cloud only (not self-hosted Jira).
What you can do with the Jira integration
Once connected, your team can:
Create new Jira tickets from Lumar tasks (choosing Jira project + issue type).
Link existing Jira tickets to a Lumar task.
Track Jira ticket status from inside Lumar (status updates appear on the task summary).
Map required and optional Jira project fields directly in Lumar, so tickets meet your project's field requirements without manual editing in Jira.
Set up the Jira integration
Before you start
The integration uses the Jira permissions of the person who connects it—so choose someone who can access the right Jira projects/boards and create issues.
If your Jira projects use required fields or custom field configurations, these will be surfaced automatically during ticket creation. No additional setup is needed beyond connecting the integration — Lumar reads field requirements directly from your Jira project settings.
Step 1: Navigate to Integrations
Log in to Lumar.
Open the user menu and select Account.
In the left-hand navigation, select Integrations. You’ll see the option to add a Jira integration.
Step 2: Create and authorize the integration
Click New Jira integration.
Give the integration a name and click Create.
You’ll be taken to an Atlassian authorization screen—click Accept to grant access.
Back in Lumar, confirm the integration shows as valid/connected on the Integrations screen.
Create or link Jira tickets from a Lumar task
Once Jira is connected, you’ll manage tickets from Task Manager.
Step 1: Open the task you want to deliver
Create a task from a Lumar report (if you haven’t already).
Go to Project Tasks to open Task Manager and click into the task you want.
Step 2: Choose whether to create or link a ticket
On the task screen, you’ll see options to:
Create New Ticket, or
Link Existing Ticket.
Link an existing Jira ticket
Select Link Existing Ticket.
Choose the Jira Authentication (if there are multiple).
Choose a ticket from the dropdown or search for it.
Click Link Ticket.
Important: Linking an existing Jira ticket does not update that ticket’s content. Lumar only sends content into Jira when you create a new ticket.
Create a new Jira ticket
Select Create New Ticket.
In the ticket modal, choose:
- Jira Authentication (if there are multiple connections)
- Jira project
- Issue type (e.g., Task, Story, Bug)
- Description field (map this to the correct field in your project)
- Delivery ticket name
Choose whether to enable Embed AI-generated ticket content
Under Project Fields, complete any fields marked as Required. These are determined by your selected Jira project and issue type, and must be filled in before the ticket can be created. Common examples include fields like Group, Care Readiness, or other custom fields your team has configured in Jira.
To add additional metadata, click + Add Optional Field and select from the available fields for your project (e.g., Components, Priority). Fill in values as needed.
Click Preview Delivery Ticket to review the ticket content before sending it to Jira.
Click Create Delivery Ticket to create it in Jira.
Working with project fields
Jira projects often require specific fields to be completed before a ticket can be created. Lumar detects these automatically based on your selected project and issue type.
Required fields appear automatically in the form, each clearly tagged with a "Required" label. You must complete all required fields before the ticket can be submitted. If a required field is left empty, the form will prevent creation and indicate what's missing.
Optional fields are not shown by default. Click + Add Optional Field to browse and add any additional fields available for your project. These can be removed individually by clicking the × next to each field.
All Jira field types are supported, including dropdowns, multi-selects, and custom fields. Values appear exactly as they do in your Jira project — so if a field uses a dropdown in Jira, it renders as a dropdown in Lumar.
Understand what gets sent to Jira
If AI-generated ticket content is OFF
Lumar creates the Jira ticket using your task’s core sections (like Description and Requirements / How to Fix). You can preview this before creating the ticket.
If AI-generated ticket content is ON
Lumar uses the details in the task to generate a more complete, consistent delivery ticket format with more developer-focused detail.
After you create the ticket
Confirm creation and view status
You’ll see a confirmation message, and the linked Jira ticket will appear on the task summary with its current Jira status.
As the Jira ticket moves through your workflow, the status shown in Lumar updates accordingly.
Open the ticket in Jira
Click the ticket ID in Lumar to open the Jira issue and view it in the correct Jira project/board. Lumar also includes a link back to the Lumar task report view in the Jira ticket.
Remove a linked ticket from a Lumar task
If you want to disconnect a Jira ticket from a Lumar task:
Click the × next to the linked ticket in the task view.
Confirm removal.
Removing the link in Lumar does not delete the Jira ticket—you’d need to delete it in Jira if required.