Last checked with GitLab: . Status comes from GitLab using a 2-minute cache. Merge events clear affected cached statuses. An already-open page does not update itself. Refresh page.

An MR completes this bounty when it is merged into main with Closes #274 and GitLab closes the issue. A mention or an updated timestamp is not completion. Awarded points appear in Activity.

Description

Tasks already store and display estimated_minutes, but TaskFilters and the marketplace sort/filter controls do not offer a time budget. Let members find a manageable session without treating missing estimates as zero.

Who might enjoy this

  • Community interests: Community / knowledge sharing, Professional development, Infrastructure
  • Skills: backend, frontend, sql
  • Experience: intermediate; work style: visual.
  • Readiness: ready; bounty size: M (existing points tier; standard merge award stacks separately).

Current behavior and starting points

Source-reviewed against main cf05b29c6256dba70d0ebc09b22cc9867cdb786a on2026-10-18. Check current main and related issues/MRs before implementing so existing work is reused.

Relevant Files

Deliverables

  • An optional bounded maximum-estimate filter using the existing minutes field and parameterized SQL.
  • Exclude unknown estimates when a maximum budget is active, label that rule visibly, and preserve the filter through pagination and other filters.

Dependencies and decisions

No prerequisite issue is required. Re-read current main and linked MRs before starting.

Acceptance criteria

  • [ ] Router/local-D1 tests with 15-, 45-, 120-minute and unknown-estimate tasks prove the selected budget and unknown handling.
  • [ ] Negative, malformed and excessive values are rejected or normalized by a documented allowlist; count and result queries use the same criteria.
  • [ ] Run Task Exchange test/typecheck/lint and verify GET filter links work without client JavaScript.
  • [ ] Record named baseline failures and the exact commands used. A behavior fix includes a real route/database/protocol check observed failing before the change. Knowledge work includes source traceability and reproducible reviewer evidence.
  • [ ] Run the affected app's existing checks. Explain any baseline failures rather than reporting a matching failure count as proof.

Try it locally

Start from the existing source files above. The following is the target demo your contribution should enable; a newly proposed script or fixture is part of the deliverable:

Use a synthetic marketplace with four estimates and find work for a 30-minute break, then compare with the full list.

Use public or synthetic examples. Starter work should run without production access; explicitly name any software/device prerequisite before claiming it is ready.

Out of scope

  • No AI duration estimates, time tracking, reward changes or member-skill recommendation system (#212).
  • Unrelated refactors, new services/providers, bulk dependency changes, production access changes, unrequested notifications, and copying private member material. Keep credentials and unresolved security findings outside the issue and repository.

For a coding agent and reviewer

Read AGENTS.md, applicable .cursor/rules/, app instructions and docs/contributing/agentic-bounty-review.md. Reuse the existing shared helpers, identity/access paths and app styling. Implement one bounded story and provide evidence the accepting app maintainer can reproduce. State updated / pre-release verified / released / live verified accurately.

A parent index carries no duplicate award for these child deliverables. Open one scoped MR using this issue's actual number after the closing keyword. Link your GitLab identity on Scoreboard; the existing merge webhook handles eligible points.

Catalog index: #258.

<!-- community-interest-bounty:2026-10-18:tasks-time-budget-filter -->

Relevant files

Hints

No hints yet.

Activity

  • +100 Hugo Zarate earned M bounty 6h ago

Comments

No comments yet. Be the first to weigh in.

↑ Top