[Feature]: New thread should default to the current sidebar project
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 23k
- Forks
- 5.9k
- Avg merge
- 11h 14m
- Merged PRs (30d)
- 357
Description
Before submitting
- I searched existing issues and did not find a duplicate.
- I am describing a concrete problem or use case.
Area
apps/web
Problem or use case
The project-scoped sidebar is great: it keeps a project's threads together with their to-do/done states. But clicking New asks me to choose a project again, even though I'm already inside one. That's an unnecessary extra click, and the current project isn't always at the top of the selector.
Proposed solution
When the sidebar is scoped to a project, New should start a thread in that project by default. Keep the project selector available to switch projects; only show it first when no project is selected.
Why this matters
The sidebar already establishes the project context. Thread creation should inherit it.
Contributor guide
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.
Research direction
Start in apps/web by tracing the sidebar's New action and project selector. Done means a thread started from a project-scoped sidebar defaults to that project, the selector remains available for switching, and the selector is shown first when no project is selected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 72/100