Improved

Jira mapping is rules now, and you can check one before you trust it

Say that bugs in a Jira project go to your Support retainer, or that anything tagged “Platform” goes to the platform project — then type an issue key to see exactly which rule wins.

The admin Jira mapping used to be one grid of dropdowns: each Jira project pinned to one workspace project. It could say exactly one thing, and it said it about every issue in the project.

It is rules now. A rule matches on a whole Jira project, one issue type within a project, or a custom field value — so "bugs in ACME go to the Support retainer" and "anything where Team is Platform goes to the platform project" are both things you can now say. A rule can name the task as well as the project.

The most specific rule always wins, whatever order you added them in: a custom-field rule beats an issue-type rule, which beats a whole-project rule. A custom-field rule describes one issue and a project rule describes thousands, so letting the general one win would make the specific one impossible to express. Two rules of the same kind are separated by an order number you set when you add the rule, lowest first — it shows on each rule as #300. It only breaks ties within a kind: a whole-project rule set to #1 still loses to an issue-type rule set to #900, because specificity is the point and an order number should not be able to quietly undo it.

Leaving a rule's project as Ask every time is a real choice, not a blank one. That rule still wins and the picker asks — which is what you want where the answer genuinely varies and a vaguer rule would otherwise answer confidently and wrongly.

Check an issue before you rely on a rule

Type an issue key into Check an issue and you get the rule that wins, the rules that also matched and lost, and the project and task the time would land on.

This is the part worth using. Getting precedence wrong is silent: the hours go to the wrong project and look exactly like somebody picking the wrong project by hand. Seeing the rule you expected to win listed as beaten is usually the whole answer.

Two things that used to go quietly wrong

A mapping to an archived project used to be returned as though it were fine. Nothing validated the target, so a project somebody archived months ago kept being handed back as the authoritative answer, and starting a timer against it either failed for a reason the picker never mentioned or landed hours on a closed project. Rules are checked when you save them, and the picker now says when a rule needs an admin's attention instead of quietly guessing something else.

A rule keys on the issue type's id, not its name. Renaming "Bug" in Jira no longer silently stops a rule matching.

Existing mappings were carried over as whole-project rules automatically. One that pointed at a project that no longer exists was dropped rather than migrated — a rule pointing at nothing is worse than no rule, because it looks configured.

The assistant can read the rules, check an issue, and add a rule for you: "which rule sends ACME-142 to Support?" or "make bugs in ACME go to the Support retainer".

← Everything that has changed

The hours, the invoices, and what they earned

Free for unlimited people. One paid plan, $10 per member per month, when you want HR, scheduling, timesheet approvals, scheduled backups, email from your own domain and scheduled reports.

Start free