Linear Integration

Connecting Linear lets DevClocked sync your Linear 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 Linear.

What gets connected

• Linear workspace — you install the DevClocked Linear app into your Linear workspace with a standard OAuth flow. No API keys to copy.
• Issue sync — DevClocked pulls your issues (identifier, title, state, assignee) into a read-only cache it can link work against.
• Evidence links — DevClocked matches the issue identifier (e.g. ENG-142) 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, moves, or edits your Linear issues.

Connect Linear

1. Open Settings > Integrations.
2. Find the Linear card and click Install Linear.
3. DevClocked redirects you to Linear's authorization screen.
4. Choose the workspace to connect and click Allow.
5. Linear redirects you back to DevClocked and the card shows Installed.

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 Linear dialog.

How issues link to your work

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

• Branch names — a tracked work block on a branch such as eng-142-fix-login is linked to ENG-142. 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 ENG-142 fix token refresh 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 Linear issues.
• Reinstall Linear — re-run the OAuth flow if the connection needs reauthorising (shown as Needs reinstall).
• Disconnect — remove the connection and stop syncing. Your DevClocked sessions and commits are untouched.

Troubleshooting

The Linear card shows "Sync error".

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

Issues aren't linking to my work.

Linking relies on the issue identifier 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.