Jira Integration

Lantern can sync issues to your Jira board with a single click. This keeps your internal development workflow in Jira while letting clients report and track issues in Lantern.

#Requirements

• The Team plan (Jira integration is not available on the Individual plan)
• A Jira account with API access
• Your Jira site URL, login email, and an API token

#Getting a Jira API token

1. Log into your Jira account.
2. Go to id.atlassian.com/manage-profile/security/api-tokens.
3. Click Create API token.
4. Give it a name (e.g. "Lantern") and copy the token.

Keep this token safe — you will not be able to view it again after closing the dialog.

#Connecting Jira to Lantern

1. In your team workspace, go to Settings → Jira.
2. Enter:
   • Jira site URL — e.g. https://yourcompany.atlassian.net
   • Email — the Jira account email
   • API token — the token you copied above
3. Click Test connection. Lantern verifies the credentials before saving.
4. Once connected, choose your:
   • Default project — the Jira project new issues will be created in
   • Default issue type — e.g. Bug, Task, Story
5. Toggle Jira integration enabled to turn it on.

Your API token is encrypted before being stored.

#Syncing an issue to Jira

Once Jira is connected, a Sync to Jira button appears on every issue.

1. Open the issue you want to sync.
2. Click Sync to Jira.
3. Lantern creates a new Jira issue with:
   • The Lantern issue title and description (formatted for Jira)
   • Labels: lantern and the client name
   • The project and issue type from your default settings (or client-level overrides)
4. The Jira issue key (e.g. PROJ-42) and a link to the Jira issue appear on the Lantern issue.

Each issue can only be synced once. If a sync fails, you can retry after fixing the credentials.

#Client-level overrides

Different clients may map to different Jira projects. You can set per-client overrides:

1. Go to Clients and open the client.
2. Go to the Jira tab.
3. Set:
   • Project — override the default project for this client's issues
   • Issue type — override the default issue type
   • Assignee — automatically assign synced issues to a specific Jira user

If no override is set, the organisation-level defaults are used.

#Sync status

Each issue shows its Jira sync status:

All sync attempts (successful and failed) are logged in the integration log, visible in Settings → Jira → Logs.

#What gets created in Jira

Lantern creates a new Jira issue with:

• Summary — the Lantern issue title
• Description — formatted in Jira Document Format, including the description, URL, browser, device, and a link back to the Lantern issue
• Labels — lantern + client name (e.g. acme)
• Issue type — from your settings
• Project — from your settings or client override
• Assignee — from client override (if set)

Lantern does not update the Jira issue after creation. Status changes in Lantern are not synced back to Jira.

#Disconnecting Jira

To disconnect:

1. Go to Settings → Jira.
2. Toggle Jira integration enabled off, or clear the credentials and save.

Existing Jira issue links on previously synced issues are preserved.

#Troubleshooting

Test connection fails:

• Check that the Jira site URL is correct (include https:// and no trailing slash)
• Check that the email matches the Jira account that generated the token
• Check that the API token has not been revoked

Sync fails after connecting:

• Check that the default project key exists and your Jira account has permission to create issues in it
• Check the error message shown on the issue
• View the full error in Settings → Jira → Logs