Jira Integration

Connecting Jira Cloud lets DevClocked sync your Jira issues and tie them to the actual work that delivered them — the coding sessions and commits already tracked in DevClocked. 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 issues to your commits and sessions using the issue key (e.g. PROJ-231) found in branch names, commit messages, and pull request references.

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 — e.g. a branch like PROJ-231-add-export.
• Commit messages — e.g. PROJ-231 add CSV export.
• Pull requests — the issue key in the PR, or commits already linked to the issue.

Matched issues appear alongside the sessions and commits that delivered them, so shipped work is tied back to what it was for. GitHub must be connected for commit- and PR-based linking — 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 commits.

Linking relies on the issue key appearing in your branch name, commit message, or PR. Make sure GitHub is connected and the relevant repositories are tracked, and that your branches or commits reference the Jira key (e.g. PROJ-231).