Closed
Bug 580996
Opened 16 years ago
Closed 12 years ago
Ability to hide/obsolete/deprecate (as opposed to highlight) comments by default (user would be able to mark them as 'noise' first)
Categories
(Bugzilla :: User Interface, enhancement)
Bugzilla
User Interface
Tracking
()
RESOLVED
FIXED
Bugzilla 5.0
People
(Reporter: knocte, Assigned: glob)
References
Details
(Whiteboard: [fixed by blocker])
There are some cases in which a bug grows in an insane manner with just "spam" bugs (like bug 61098) or with comments that are just a result of an error on the user's part (like bug 569400 comment 47, although maybe Bugzilla should have detected this abnormal quotation too -- be sure to file that as a different bug). So, in a similar vein as bug 259452, there should be a way to hide these comments by default for every user of more than 1 user agrees on marking the comment as "noise".
| Reporter | ||
Comment 1•16 years ago
|
||
s/"spam" bugs/"spam" comments/
Comment 2•16 years ago
|
||
Yeah, agreed. Once we have a system for tagging comments, we can set up a system for hiding comments with certain tags.
Depends on: 259452
Updated•16 years ago
|
| Reporter | ||
Updated•15 years ago
|
Summary: Ability to hide (as opposed to highlight) comments by default (user would be able to mark them as 'noise' first) → Ability to hide/obsolete/deprecate (as opposed to highlight) comments by default (user would be able to mark them as 'noise' first)
Comment 3•15 years ago
|
||
For me it would be good enough to collapse a comment permanently.
Since comment is only collapsed, and everyone can expand it again, there is no need to have complex rules to decide if a comment should be hidden. Everyone should be able to collapse or expand a comment that he thinks is (or isn't) noise, permanently, for all users. Every user can expand to check if collapse was justified.
The current collapse mechanism I consider useless, because it is not permanent, and not for all users.
this has been implemented as part of the work on bug 793963.
You need to log in
before you can comment on or make changes to this bug.
Description
•