What this section is for
After connecting a tracker, tasks appear with statuses, types and assignees. Open a task to see linked code changes. Links are found using the issue key in a branch name, commit message or pull request title. Work done without the key may not appear among the links.
When to use
- To see which code changes are linked to a task.
- Before a demo, to compare task statuses with pull requests.
- When choosing tasks for an initiative in Planning.
Quick start
- 1Connect a work tracker in Settings → Work Trackers.
- 2Filter by status, type or assignee, or search by key or title.
- 3Open an item and read Linked Code Activity — commits, pull requests and deployments attached to it.
- 4If no changes are linked, check the issue key, sync status and work done outside Git. A missing link does not mean a task has not started.
Key settings
| Setting | What it does | How to use it | Common mistake |
|---|---|---|---|
| Filters | Narrow the list by status, type and assignee. | Select in-progress tasks and check their update dates and linked changes. | Assuming the unfiltered list reflects the whole backlog — it reflects the projects the integration syncs. |
| Issue key convention | Determines whether commits and pull requests can be matched to a ticket. | Include the issue key, such as PROJ-123, in the branch name, commit message or pull request title. | Expecting links to appear for a team that references tickets only in the pull request description. |
Usage example
Scenario: Several tasks have been In Progress for more than a week.
- 1Select In Progress and check task update dates.
- 2Open the tasks and inspect linked commits and pull requests.
- 3For open pull requests, check review status. Where links are missing, check naming and sync, then ask the assignee about progress.
What this shows: You have separated review questions from data-linking problems and can check each task with its assignee.
FAQ
Why does a ticket show no linked activity?
Check the issue key in the branch, commits and pull request title, and check the last sync. Code may have changed without the key, and some work may not require Git changes at all.
Why are some projects missing?
The integration syncs the projects it has access to. Check the connection in Settings, including the token’s scope and the last sync time.
How often does it sync?
Work trackers refresh on a schedule, less frequently than Git providers. Recent changes may take a while to appear; you can trigger a sync by hand from settings.
Tips
- Agree a consistent way to include issue keys and test it on a few changes.
- If many tasks have no linked code, check setup and naming first. Missing links cannot measure people’s work.