From time to time, by using Roon, I come across an unexpected behavior in the software. As long as the behavior is bothering me enough and persists or is reproducible, I start wondering if it is an actual issue with the software.
First natural thing to do I feel is to browse through the available knowledge base (Roon forum), to see if my issue has already been documented. Currently, I am able to browse through all the individual support threads (incidents) created in the forum but do not seem to be able to easily filter out (longstanding) accepted but yet-to-be-resolved problems (known errors).
Am I wrong on the above? Having each known error documented including workaround could potentially:
- Decrease amount of support or feature request threads.
- Improve enduser satisfaction through even more accessible knowledge base.
- Improve enduser satisfaction by allowing endusers to form more realistic expectations about what is (not) to be addressed by Roon team.
The above could be achievable by having a dedicated Roon forum tag/category. (Similarly to “Feature Requests”, there could be “Known Errors” mark assignable by Roon forum staff. The most recent or critical known errors could also be pinned for improved visibility within the forum.)
As an example, one candidate for a known error: Not getting Artist Search results
If indeed not possible to search for known errors in the forum, please mark this thread as “Feature Requests”.