The Programs date range moves some numbers on a card but not the ones beside them
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 65/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- nextjs, postgresql, typescript
- Domain
- backend-api-design, data-visualization, frontend
Research direction
Look at the /programs page component and the data fetching logic for the date range filter. Identify which numbers are updated (like 'Open cases') and which are static (rate, status chips). Check the backend API endpoints that serve these metrics to understand the data scope. Verify the trend box rendering logic for empty states. The fix involves aligning all displayed numbers with the selected date range or clearly labeling the discrepancy.
Written by the indexing model from the issue text.
Description
On /programs, the date range filter changes some numbers on a card but not the ones next to them. Found in a live walk-through of the Maui sandbox as a case manager, 2026-09-23.
What happens
- "Last 7 days":
- The rate and the status chips do not change.
- The "Open cases (N)" count and the open-case total do: 15,872 open cases drops to 1,896.
- One card then reads "Overdue 1,655" next to "Open cases (384)", and another "Overdue 426" next to "Open cases (7)".
- Any range other than "All time": the small trend box becomes an empty rectangle, with no "Trend appears after a few more runs" message.
Why it matters
The chip and the link next to it describe different populations, and nothing on the card says so. A reader will conclude one of them is wrong.
Decision needed
- Scope every number on the card to the range.
- Scope none of them, and remove the range control from Programs. Measure rates are measurement-year figures, so a 7-day range has little meaning for them.
- Keep the split, but label the range-scoped numbers ("opened in the last 7 days").
Until this is decided, avoid changing the range in a demo.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- Avg merge
- 4h 20m
- Merged PRs (30d)
- 104
Getting set up
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Taleef7/workwell
-
frontend maui-pilot pilot-ask question
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
documentation owner-ops waiting
Difficulty 1/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
owner-ops waiting
Difficulty 1/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
backend enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
Maintainers usually reply within 1 day
-
backend maui-pilot webchart-convergence
Difficulty 4/5 3-5 days Newbie friendliness 68/100
Maintainers usually reply within 1 day
All issues in Taleef7/workwell
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
opengovsg/FormSG#10118 · 1 comment ·
Maintainers usually reply within 1 day
-
ai-driven-qa bug claude
Difficulty 1/5 Under an hour Newbie friendliness 75/100
linagora/twake-calendar-frontend#1434 · 1 comment ·
Maintainers usually reply within 1 day
-
check:passed streams:add
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
iptv-org/iptv#52824 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 Half a day Newbie friendliness 78/100
jaegertracing/jaeger-ui#4512 ·
Maintainers usually reply within 1 day
-
area:ide documentation enhancement platform:macos platform:vscode
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
anthropics/claude-code#97389 ·
Maintainers usually reply within 1 day