For developers · App internals
Overview status model
Every open issue in the overview has exactly one status. Code: crates/core/src/status.rs.
Statuses and recommended labels#
| Status | Standard label | Derived when |
|---|---|---|
open | status/open | nothing else applies |
in_progress | status/in-progress | the issue has an assignee |
in_review | status/in-review | an open pull request closes it (Closes #N) |
blocked | status/blocked | never derived, label only |
needs_user | status/needs-you | an open question to the user exists |
Standard labels match case-insensitively.
Precedence#
- Label mapping of the account (label name to status).
- Standard labels from the table.
- Derivation from forge data, checked in this order: open question to the user, linked open
pull request, assignee, otherwise
open.
If several labels of one tier match, the most urgent status wins (blocked, needs_user,
in_review, in_progress, open), so the label order never matters.
Derivation works on the data every adapter already reports (Forgejo/Gitea, GitHub, GitLab).
Mapping#
Stored in settings.json as status_mapping: account id to an object {"<label>": "<status>"}.
It is part of the settings backup (docs/settings-backup.md); files without the key load unchanged.
Mappings of removed accounts are dropped on load, label names are trimmed and compared
case-insensitively.
Stale threshold#
Stored as stale: {"days": 3, "repos": {"<account id>": {"<owner/repo>": <days>}}}. An open
issue without activity for days counts as stale; a repo entry overrides the global value.
0 or a missing key means the default (3 days), values are capped at 365, overrides of removed
accounts are dropped.
Settings page#
Settings, group "Work", row "Overview" (settings-leitstand) opens the page
settings-leitstand-page:
- Stale: the global value (
settings-leitstand-stale-days-input), then per account a list of the account's repos (settings-leitstand-repos-<account>); each repo has a days field (blank = same as all repos) and a reset button (…-reset, disabled without an own value). - Labels per account (
settings-leitstand-mapping-<account>-<status>-input): your own labels per status, comma separated, with the recommended standard label shown below. A label entered for one status moves away from another, so it never stands for two.
Fields save on blur or Enter through save_settings. Changes apply without a restart: when the
mapping or the stale settings change, save_settings marks the cached overview data outdated, and
the restarted account loops fetch it again on their next poll instead of after five minutes.
For the UI#
RepoCounts.issues (dashboard rows) lists the open issues per repo with status.status and
status.source (mapping, standard_label, derived).