Jira Cloud integration

The Jira Cloud integration lets you create or link Jira issues from an Action Log action, then keeps summary, status, and assignee in sync so your team sees updates on the action timeline.

Setup works in three layers: an Atlassian OAuth app and account connection, a per-project mapping (Jira project and default issue type), and then individual action links.

Recommended setup flow

1. An account admin configures an OAuth 2.0 (3LO) app in the Atlassian developer console and adds the Client ID and secret at Account settings → Integrations (Jira). The Atlassian app must allow classic Jira scopes including read:jira-work, write:jira-work (required to create issues), manage:jira-project, read:jira-user, and offline_access for refresh tokens. The OAuth callback URL in Atlassian must match your Action Log API's /api/jira/connections/oauth/callback address.
2. On Integrations, use OAuth apps on the Jira card to register one or more Atlassian OAuth applications (each with a display name, client ID, and secret), then Add connection and Connect with Atlassian to authorize each Jira Cloud site. When several apps exist, pick which app to use for that connection. If your Atlassian account can access more than one site, you will be asked to pick the site to connect.
3. From a project, open Integrations in the project menu and choose Configure on the Jira card (or open the project's Jira page). Select the connection, the Jira project, and a default issue type for new issues.
4. From an action, open the Jira panel to create a new issue or paste one or more Jira issue keys or browse URLs to link existing ones. An action can link up to 20 Jira issues; use Add Jira issue to link another.

Account connection

After connecting, the site appears under Account settings → Integrations where you can test, edit display name and project availability, or delete it. Each connection can be limited to specific Action Log projects or made available to all.

Project mapping

• Jira project: Issues are created in this Jira project when you use Create in Jira from an action.
• Default issue type: Used when creating from an action unless you pick another type in the panel. It must be valid for the selected Jira project.

Linking from an action

• Create in Jira: Action Log creates an issue using your summary text and the selected issue type. The action description is sent as the starting Jira description when you do not override it.
• Link existing: Enter an issue key (for example PROJ-123) or a Jira browse URL to link an issue that already exists.
• When a link exists, a Jira icon appears on the action so the team can see it in list and board views.

Sync behavior

• Linked actions are checked hourly in the background. When Jira reports changes to summary, status, or assignee, an update is added to the action.
• You can use Refresh in the Jira panel on an action at any time. If changes are detected, your team can receive a notification (same pattern as other integrations).
• Action Log does not change your Action Log action status from Jira. Action statuses stay under your team's control.

Reconnect (re-authorize without losing links)

On Account settings → Integrations, each Jira connection has Reconnect. Use it to run Atlassian OAuth again on the same Jira Cloud site so new tokens (and scopes) are stored. Project mappings and action links stay attached to that connection.

Removing an account connection

Deleting a Jira site from account settings is destructive: Action Log removes every project's Jira mapping that pointed at that site and every Jira issue link on actions that used the connection. The app asks you to confirm before deleting.

While a connection remains, access tokens are refreshed in the background (including rotated refresh tokens from Atlassian). Remove the site only when you must point Action Log at a different Jira Cloud site, move billing accounts, or when Reconnect cannot restore access.

Troubleshooting checklist

• If creating an issue returns Unauthorized or scope does not match, confirm the Atlassian OAuth app includes write:jira-work, then use Reconnect on that site under Account settings → Integrations so tokens pick up the new scopes without clearing mappings. Remove and add the site only if you must switch to a different Jira Cloud site.
• If the Jira panel shows a generic error, open the message for detail from Jira (for example invalid issue type or project permissions). Confirm the Jira user can create issues in the mapped project.
• If no connection appears for the project, verify an account connection exists and is scoped to include this Action Log project.
• If linked issue details look stale, wait for the next hourly sync or use Refresh on the action's Jira panel.