Task Attribution Rules
Task attribution links Git activity to tracker tasks automatically. The system finds the task key (PDM-123) in branch names, merge request titles, and commit messages.
Where to find it
Settings → Integrations → Task attribution.
How it works
Rules are organized into three groups:
| Group | Searches the key in |
|---|---|
| Branch | Branch name |
| MR Name | Merge request title |
| Commit Name | Commit message |
How rules apply:
- Up to 20 regexes per group.
- Rules run top to bottom until the first match wins.
- The task key = the first pair of parentheses in the matched regex.
- Empty group → built-in rules apply.
- Filled group → your rules replace the built-in ones completely.
Examples:
| Regex | Result |
|---|---|
feature/(PDM-\d+) | Extracts PDM-123 from feature/PDM-123-login |
(?i)\b([a-z]+-\d+)\b | Matches keys in any letter case |
Recognition percentage
The green percentage shows how much of the last 30 days is recognized.
- Updates live as you type.
- Hover it to see unrecognized branches.
- Each rule shows its own match count.
AI Autofill
Requires a connected AI provider. Autofill studies your branches, MRs, and commits over the last 30 days and fills the fields for you.
It saves nothing — review the suggestions and press Save.
After saving
Test connection— recalculates the results.Save— applies the rules.
Only unlinked branches are re-matched after saving. Already linked ones never change, and charts lose nothing.
FAQ
Why does MR Name show 'No data'? MR titles accumulate after the server update — this is normal.
Which part of the regex becomes the task key? The first pair of parentheses.
Will saving change existing links? No. Only unlinked branches are re-matched.