Actions
Feature #114
openTask and Project Statuses
Status:
Open
Priority:
High
Assignee:
-
Target version:
-
Start date:
01/11/2026
Due date:
% Done:
0%
Estimated time:
Engineering Effort:
App Component:
API
Feature:
Description
The project has need of many statuses for projects and tasks
| Status | Meaning |
|---|---|
| open | Defined and ready for action |
| waiting | Blocked on something external (delivery, coworker, etc.) |
| deferred | "Someday/maybe" — not committed to doing it now |
| declined | Decided not to do; kept for record but inactive |
| stale | No action in a while; needs review |
It's tempting to shove this into an enum and enforce it at the database level, but we may want to update the list of statuses- this first draft is unlikely to be ironclad forever
Maybe we should achieve this with a simple string field and conventions, but eventually we'll want to formalize something around this.
Updated by Sam Pearson 6 months ago
backlogged because this is practically a whiteboard party
Updated by Sam Pearson 23 days ago
- Status changed from Backlogged to Open
- Priority changed from Normal to High
- App Component set to API
Setting this to high prio for now because there are one of two outcomes:
- this is already handled with dedicated status endpoints rejecting requests for invalid statuses
- that's what needs to happen but it isn't done yet.
Checking into this should be high prio and then we can re-evaluate after we know, but there's a good chance this ticket gets dropped because the work is already done.
Actions