Addition of a new Quick Issue Capture issue type #3857
Description
What problem does this proposed feature solve?
We follow an issue-first approach, but currently if I want to break out a small chunk of work like a refactor it must be ticketed as a detailed feature proposal or bugfix, which isn't really the right fit. As a result I've felt nudged towards fitting these types of things inside other PRs, which has led to them ballooning in scope.
Also the high friction to add any issue has led to me capturing issues locally for myself in a backlog, which isn't useful to the community as it is only visible to me.
Finally, there is an explosion of agentic tooling around github issues - we may be able to have rough or loosely captured issues automatically deduped, expanded upon, or even agentically coded to completion with first-pass code ready to review by the time we see the issue.
Describe the proposed solution in detail
Add a new issue type that is a super loose Quick capture with only a title, basic categorization, and a single text field
Technical considerations or implementation details (optional)
Users should still be pointed towards the existing bug and feature proposal issue types where appropriate.
Describe alternatives considered (if any)
No response
Additional Context & Mockups
PR out #3858 with a potential lowest-friction-possible issue type
Proposal Checklist
- I have searched existing Issues and Discussions to ensure this proposal is not a duplicate.
- This proposal is for a specific, actionable change intended for implementation (not a general idea).
- I understand that this proposal requires review and approval before any development work begins.
Are you interested in implementing this feature if approved?
- Yes, I would like to contribute to implementing this feature.