https://bugs.documentfoundation.org/show_bug.cgi?id=156401
Bug ID: 156401
Summary: this is a comment/feature request about the bug
reporting system itself
Product: LibreOffice
Version: 7.5.4.2 release
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: enhancement
Priority: medium
Component: LibreOffice
Assignee: [email protected]
Reporter: [email protected]
Description:
I have filed several bugs/reports over the years. But when I log in, in "my
bugs" I only see a few of them. Apparently, when the reported bug is duplicate
(also true for other status, not sure exactly which ones), the bug is erased
from my list (or never made it to the list) and, if I don't search actively, I
never know what happened to that report. I think this kind of discourages
people from reporting.
Steps to Reproduce:
1. log in to the bug reporting system.
2. File a bug.
Actual Results:
1. sometimes (eg I guess when your bug has not been previously reported?) the
bug will be listed in "my bugs"
2. other times (eg I guess when it is duplicate) the report does not even
appear in your "my bugs" list
3. If the report never made it to the "my bugs" list, and you want to know what
happened to the bug you reported, the only way to know is either to save the
URL at the time of the report, or by a convoluted search in "advanced search"
(which, at this time I tried and didn't work [I searched by people using my
email and I got hundreds and hundreds of bugs, unrelated to my activity]).
Expected Results:
It would be nicer that all reports to appear in the "my bugs" list. If you
don't want to call them bugs (because some are not) then they could be named
"my reports" or "my activity". This way the user can see whatever happened to
the report only by logging into her account, no need for a convoluted search.
Reproducible: Always
User Profile Reset: No
Additional Info:
My point is that showing what happened to the report is a way of giving
feedback to the user, and not showing what happened to it is a lack of
feedback, which results in discouraging the user: why would I report something
if I have no idea what happened to it? the user is benefited by being informed
if the bug was not a bug, or duplicated (and then she/he can read the original
report, etc.) or any other change of status. If the user knows that no feedback
will be easily available, then next time maybe it will not report (why
bother?).
I am not criticizing anything and I will keep reporting even if I have to
actively search for the feedback, but it is sensible to consider that not
everyone is like that and they like to have feedback to engage.
--
You are receiving this mail because:
You are the assignee for the bug.
