Description of the limitation and why it is relevant to address
As a Maintainer I want to see a list of all the bug and users’ problem reports, so that I can find my errors more easily and do version/error control.
I think this is relevant for the VIKTOR platform because at the moment, finding a report as a maintainer requires finding the corresponding email and clicking the link, which is unpractical.
Submitter proposed design (optional)
For each app, in the developer section, add a Reports tab (next to Versions and Variables) with a list of the reports, with their date, user and maybe the first few words of the error message.
Current workarounds
Saving the URL of each report in a file and click on them. This isn’t very practical and requires constant updating.
Hi Remi, thanks for contributing to the community forum!
I think the following feature request is close to what you want: Gathering and upvoting of user feedback within applications - #2 by mslootweg.
You can consider upvoting that and adding your thoughts
Hi @matthijs, thanks for your comment!
I believe that Kazarian’s feature request is focused on user feature requests, and does not include bug/problem reports, hence my feature request.
However I hadn’t seen Wichard’s comment at first. I’ve added my own comment at the bottom to recap.
Would you prefer I keep my feature request - focused on bug/problem reports (and perhaps link it to Kazarian’s) - or simply remove it as it is redundant with Wichard’s comment?
thanks for adding the context there too.
the features are now linked, so no extra actions are needed.
I think it’s fine to leave this open. a solution targeting all at once feels most logical to me, but we might also split it in separate developments.
1 Like