Closing the feedback loop
|Opened on:||Thursday, December 23, 2021 - 00:56|
|Last modified:||Saturday, December 25, 2021 - 01:36|
The feedback logs for suggestions, bugs, etc. are transparent and comprehensive, but it's difficult to see if a bug or suggestion that a user is about to make has already been reported, fixed, tested or released. - Some users report many items in a single post, making the open/closed field ineffective. - And the occasional, disappearing, one-time news narrative at a "new release logon-download" seems to be the only place that a fixed-bug description appears.
This may be a lot to ask, but why not put some kind of abbreviated issue management list somewhere in the feedback area? It would be a good way to manage expectations and would save both users and staff a lot of time currently wasted scouring the feedback area for information buried in the many and various tabbed items.
Closing the feedback loop is a good practice. Even closing an issue with an answer like "It's trivial. No. Get over it," is better than no answer at all.