What this section is for
Connect a tracker to import tasks and use them in planning. Jira needs an Atlassian email, API token and server address; Linear needs an API key; Azure DevOps needs a personal token with work item read access.
When to use
- When you want tickets linked to the code that implemented them.
- Before choosing tasks for an initiative in Planning.
- When cost classification needs task types and other task data.
Quick start
- 1Create a token with read access to projects and issues.
- 2For Jira, enter the Atlassian account email and the server URL for your instance; for Linear, the personal API key; for Azure DevOps, a PAT with work item read scope.
- 3Run the first sync and check the sync status and project count.
- 4Confirm in Work Items that issue keys are being matched to branches and pull requests.
Key settings
| Setting | What it does | How to use it | Common mistake |
|---|---|---|---|
| Server URL | Sets the base address of your tracker. | Copy the base address with https://, without a path to an individual task or API. | Entering a task page or API endpoint instead of the tracker base address. |
| API token scope | Determines which projects and issues can be read. | Read access to projects and issues is enough. Nothing here writes back to your tracker. | Restricting the token to one project and expecting the others to sync. |
Usage example
Scenario: Work Items shows tickets from one project but the team works across three.
- 1Check the project count reported on the connection after the last sync.
- 2Verify that the token has access to all three projects in the tracker itself.
- 3If needed, grant access to the required projects, update the connection and sync again.
What this shows: Tasks from all projects you authorised are now available.
FAQ
Why are issues not linking to commits?
Check the issue key in the branch name, commit message or pull request title. Without it, a link may be missing even when both connections work.
Does it write anything back to the tracker?
No. These connections are read-only.
Why is the sync status showing an error?
Usually an expired token, a changed instance URL, or permissions removed on the tracker side. The connection card shows the last sync time and status.
Tips
- Agree where to include issue keys and check one linked example after syncing.
- A recent task may take time to appear. Check the last tracker update or run a sync manually.