chartStatus should be reworked to be just currently open, pending, in progress tickets as a breakdown as over time closed will take up 99% of it. #110

New Issue

2026-09-11T12:27:31-04:00

jared commented

2026-09-11 12:27:31 -04:00

No description provided.

jared added the invalid priority/low ux labels 2026-09-11 12:27:31 -04:00

jared referenced this issue from a commit

2026-09-11 22:23:44 -04:00

Exclude Closed tickets from the dashboard status breakdown chart (#110)

jared referenced this issue from a commit

2026-09-11 22:26:38 -04:00

Merge development into main: dashboard status chart excludes Closed (#110)

jared commented

2026-09-11 22:26:48 -04:00

Fixed in commit 78ee5fd (merged to main in b73a4c7).

StatsModel::getAllStats()'''s by_status breakdown grouped every status including Closed, unlike by_priority and by_category which already filter status != '''Closed'''. Closed tickets accumulate indefinitely, so over time the status donut chart'''s Closed slice comes to dominate it, squeezing Open/Pending/In Progress down to barely-visible slivers -- exactly the breakdown the chart exists to show at a glance.

Filtered by_status the same way the other two breakdowns already are. The separate open_tickets/closed_tickets KPI counts are unaffected (a different query); Closed just no longer appears as a chart segment.

Note on the '''invalid''' label: checked and found no explanation in the issue body or comments. It'''s Gitea'''s generic stock label (description "Something is wrong"), not a documented decision that the request itself was wrong -- the described problem was real and reproducible in the code, so implemented it as filed. If it was meant to convey something else, let me know.

Verified against real MariaDB: seeded 3 open-ish tickets (Open, Pending, In Progress) and 3 Closed. by_status now returns only the 3 active statuses; open_tickets/closed_tickets KPI counts are unchanged at 3/3.

Fixed in commit 78ee5fd (merged to main in b73a4c7). StatsModel::getAllStats()'''s by_status breakdown grouped every status including Closed, unlike by_priority and by_category which already filter status != '''Closed'''. Closed tickets accumulate indefinitely, so over time the status donut chart'''s Closed slice comes to dominate it, squeezing Open/Pending/In Progress down to barely-visible slivers -- exactly the breakdown the chart exists to show at a glance. Filtered by_status the same way the other two breakdowns already are. The separate open_tickets/closed_tickets KPI counts are unaffected (a different query); Closed just no longer appears as a chart segment. Note on the '''invalid''' label: checked and found no explanation in the issue body or comments. It'''s Gitea'''s generic stock label (description "Something is wrong"), not a documented decision that the request itself was wrong -- the described problem was real and reproducible in the code, so implemented it as filed. If it was meant to convey something else, let me know. Verified against real MariaDB: seeded 3 open-ish tickets (Open, Pending, In Progress) and 3 Closed. by_status now returns only the 3 active statuses; open_tickets/closed_tickets KPI counts are unchanged at 3/3.

jared closed this issue

2026-09-11 22:26:48 -04:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: LotusGuild/tinker_tickets#110