[Feature Request]: Add a new option for reporting insights

[fcoveram]

"What": What is your idea?

Add a fourth option in the reporting list for sharing insights that users consider inconsistent with the task they want to complete.

"Why?": Why would this be impactful?

Reporting insights as a user without requesting features helps to connect ongoing tickets and/or identify room for improvement of current features. Contrary to reporting bugs, sharing an user insight is an input that outlines what the individual wants to achieve and what encounters.

It's a fast-following approach to polish products.

"How?" How should this feature work?

In the "Report an issue" selector, add a new type for "User insight" connected with existing templates or blank issues.

[jeherve]

Wouldn't we want to immediately "convert" that user feedback or insight into a potential enhancement, feature request, or a bug report? User feedback is very important, but I feel like it should be grouped into a matching product change for it to be useful. That way, if multiple site owners report the same insights, we know that enhancement or feature request is more important.

[fcoveram]

User feedback is very important, but I feel like it should be grouped into a matching product change for it to be useful

I agree that requesting a feature is more useful, but for users who just want to report an odd situation in their flow, it's a big effort dive into the product, understand ongoing changes, and sharing a design that is coherent; as it's currently my case.

Our conclusions might come from different backgrounds, and given that Github is primarily for tracking code work and decision around it, the "sharing an insight" need is a real need in the design process where discovering user friction plays a key role.

Adding the option would depend on how broad the report collection is.

[jeherve]

the "sharing an insight" need is a real need in the design process where discovering user friction plays a key role.

That makes perfect sense. In a way, that's how all product changes start.

imo I think it's fine to share some feedback and tag it as "enhancement" or "bug fix" based on your first gut feeling when opening the report. That's fine if you do not have a fully fledged solution yet. Discussion can then happen on the issue, and it can be re-classified later as a bug or an enhancement based on the discussion.