Issues / #51
Make category and project fields optional by default when reporting issues
proposed
improvement
Priority: low
Project: nimsforestissue
Reporter: anonymous
21 Mar 2026 14:45
Description
When reporting a new issue via the web form, the category and project fields should be optional (empty by default) rather than requiring a selection. This reduces friction for reporters who may not know the correct category or project, and lets the grooming process handle triage.
Comments (1)
nebula
21 Mar 2026 14:59
Grooming: changed category from bug to improvement, set priority to low, changed project from cindy to nimsforestissue, rewrote title and description
Nebula's reasoning: This is a UX improvement to the issue reporting form, not a bug — the current behavior works, it just creates unnecessary friction. Assigned to nimsforestissue since it's about the report form. Low priority because the grooming process already handles miscategorized issues, so this is a nice-to-have rather than a blocker. Rewrote the truncated title and expanded the description to clarify the expected behavior.
Nebula's reasoning: This is a UX improvement to the issue reporting form, not a bug — the current behavior works, it just creates unnecessary friction. Assigned to nimsforestissue since it's about the report form. Low priority because the grooming process already handles miscategorized issues, so this is a nice-to-have rather than a blocker. Rewrote the truncated title and expanded the description to clarify the expected behavior.