Mapping source statuses onto board statuses
Every synced item arrives with a source-side status — a Jira status, an ADO state, a GitHub label or open/closed state — and the mapping editor decides which of your board's own statuses that becomes. Leave a value unmapped and nothing gets dropped; the sync falls back to a sensible default instead.
Each row is a real value pulled from synced data, not a guess.
What it does, and where the data comes from
The choices on the left side of the editor aren't a fixed enum — they're the distinct values your synced data actually contains, queried live per provider:
| Provider | Source field queried | Notes |
|---|---|---|
| Jira | distinct status on synced issues for the project | Whatever status names your workflow actually uses |
| Azure DevOps | distinct state on synced work items for the project | Custom process templates show their own state names |
| GitHub | distinct issue labels, plus the synthetic open and closed | GitHub has no status field — labels and open/closed state are all there is |
Values already in your saved mapping stay listed even if they haven't appeared in a recent sync, so editing an old mapping never silently loses a row.
How to edit a mapping
- Open a board's Source zone for the connection and choose Status mapping.
- For each source value, pick a board status from the dropdown, or leave it as — unmapped —.
- Save changes persists the mapping; Clear all mappings resets every row back to unmapped in one click.
Under the hood
Matching is case-insensitive for all three providers — "In Progress" in your mapping matches a source value of "in progress" or "IN PROGRESS" equally. This matters most for GitHub, where the promotion path checks an issue's labels against the mapping first, then its open/closed state, all case-insensitively, before falling any further.
All three providers ship with a sensible default mapping already filled in when a sync is first created (Jira: To Do/Open/Backlog → Not Started, In Progress/In Review → In Progress, Done/Closed/Resolved → Done, and so on; GitHub: open → In Progress, closed → Done). You're editing on top of that default, not starting from a blank slate.
If it looks wrong
| Symptom | Cause | Fix |
|---|---|---|
| A GitHub issue lands in an unexpected board status | One of its labels matched the mapping before its open/closed state was checked | Remember labels are checked first — remove or remap the conflicting label |
| A brand-new board status keeps appearing | A source value with no mapping and no case-insensitive name match on the board | Map it explicitly, or rename the auto-created board status and map future occurrences to it |
| A status you know exists isn't in the picker | No synced item has carried that value yet | Wait for a sync to observe it, or add the mapping manually once it appears |
Related
- Connecting Jira, Connecting GitHub, Connecting Azure DevOps — provider setup pages.
- Boards — how board statuses themselves work.
- In-progress statuses — a related but separate status classification, used for timesheet hours.
Last updated