The board
Urgency
A score decides what comes first. It is the sum of three things, each shown on the board.
the formula
urgency = (100 − rule priority) + waiting + ticket
The three parts
| Part | Points | From |
|---|---|---|
| Rule | 100 − priority | The rule that lists the task. A review to do (priority 10) gives 90; a draft to finish (priority 90) gives 10. |
| Waiting | 3 per day, at most 60 | The full days since the next step arrived: since the review was requested, since the oldest unanswered reply, since your last word when you wait on someone. |
| Ticket | +5, plus the priority | A change that names a ticket in its title or branch (PROJ-12) gets 5, plus the points of the ticket's priority when Jira can tell it. A ticket gets the points of its own priority. |
| Ticket priority | Points |
|---|---|
| Highest | +50 |
| High | +30 |
| Medium | +10 |
| Low | 0 |
| Lowest | −10 |
An example
i on a task
HOW ITS URGENCY ADDS UP rule 80 "Re-review" has priority 20 (0 first, 100 last): 100 − 20 waiting +15 5 days × 3 a day ticket +35 tied to PROJ-440, "high" (+30), and +5 for naming a ticket urgency = 130 hot: warm ▴ from 100, hot ▲ from 130
Where the board shows it
- The detail pane sums it up:
urgency 130 = rule 80, waiting +15, PROJ-440 (high) +35. - Panes ordered by urgency show the score on every line.
- i on a task lays it out line by line, with your own weights.
▴marks a task from 100 points (warm),▲from 130 (hot). The filterheat:hot,warmkeeps them.
Orders
Panes list the most urgent first by default. s changes a pane's order and v reverses it.
| Order | First |
|---|---|
urgency | The highest score; among equals, the one that has waited longest. |
rule | The rules' own order; among equals, the freshest. |
waiting | What has waited longest. |
updated | What moved most recently. |
created | What was opened first. |
Change the weights
~/.config/aki/config.toml
[urgency] per_day = 3 waiting_cap = 60 linked = 5 highest = 50 high = 30 medium = 10 low = 0 lowest = -10 warm = 100 hot = 130
The rule's part follows the rule's priority: change it under [rules.<name>]. aki rules prints the weights in use.
How a change is tied to a ticket
By a key in its title or branch name, such as PROJ-12. With a Jira source configured, the key is looked up, even for tickets that are not yours, and its priority counts. Without one, anything shaped like a key counts as a ticket and gets the 5 points.