Jira Integration

Connecting Jira Cloud lets DevClocked sync your Jira issues and match their issue keys to tracked branches, commits, and pull requests. It's a read-only, OAuth-based connection: DevClocked never changes anything in Jira.

What gets connected

• Jira Cloud site — you authorise DevClocked against your Atlassian account with a standard OAuth flow and pick the Jira site to connect. No API tokens to copy.
• Issue sync — DevClocked pulls your issues (key, summary, status, assignee) into a read-only cache it can link work against.
• Evidence links — DevClocked matches the issue key (e.g. PROJ-231) in branch names, commit messages, and pull request branches to the tracked work that contains it.

The connection is read-only: writeback is disabled, so DevClocked never comments on, transitions, or edits your Jira issues.

Connect Jira

1. Open Settings > Integrations.
2. Find the Jira card and click Connect Jira.
3. DevClocked redirects you to Atlassian's authorization screen.
4. Choose the Jira site to connect and click Accept.
5. Atlassian redirects you back to DevClocked and the card shows Connected.

DevClocked runs a first sync automatically. After that, issues re-sync on a schedule (roughly hourly), and you can trigger an immediate refresh at any time with Sync issues in the Jira dialog.

How issues link to your work

Once issues are synced, DevClocked links them to your tracked work using the Jira issue key:

• Branch names — a tracked work block on a branch such as PROJ-231-add-export is linked to PROJ-231. The issue is then shown with the session containing that work block; this is not a direct session-level attachment.
• Commit branches and messages — a key in the commit branch or a message such as PROJ-231 add CSV export links the issue to that commit.
• Pull requests — a key in the pull request's head branch, or commits already linked to the issue, adds pull-request evidence when the issue is viewed.

File names and file paths are not scanned. If an issue key appears only in a file name or path, DevClocked will not create an automatic link. A direct attachment to the top-level session can be added manually from the session's issue picker.

Issue linking runs in the background every 30 minutes and checks recent tracked work from the previous 14 days. An already-synced issue can therefore take up to 30 minutes to appear automatically. Cross-team or cross-project matches are kept as suggestions until you explicitly confirm them.

GitHub must be connected for commit- and pull-request-based evidence — see Connecting GitHub.

Managing the connection

• Sync issues — force an immediate re-sync of your Jira issues.
• Reconnect Jira — re-run the OAuth flow if the connection needs reauthorising (shown as Needs reconnect). Atlassian access is refreshed automatically in the background between reconnects.
• Disconnect — remove the connection and stop syncing. Your DevClocked sessions and commits are untouched.

Troubleshooting

The Jira card shows "Sync error".

Open the Jira dialog to see the error detail. A common cause is an expired authorization — click Reconnect Jira to reauthorise.

Issues aren't linking to my work.

Linking relies on the issue key appearing in a tracked branch, commit branch or message, or pull-request branch. Make sure GitHub is connected and the relevant repositories are tracked, and do not rely on the key appearing only in a file name or path.