Closed Bug 324647 Opened 20 years ago Closed 19 years ago

Allow for marking posts as off-topic

Categories

(Bugzilla :: Bugzilla-General, enhancement)

enhancement
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 283695

People

(Reporter: raceronline, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1 In public bugzilla databases, A) off-topic messages, B) unhelpful complaints, C) repeated information, and D) spam in general can clutter up a popular bug to be beyond readability. There needs to be a system to allow selected users to mark posts as "off-topic" (which would include any of the above four categories). I. This marking could be done by the A) bug reporter, B) qa contact, C) assignee, D) module owners, E) drivers, and perhaps F) a moderator group. Also, people in these groups could not have their posts be marked "off-topic". II. The list of who actually has the authority to mark users off-topic should be a configurable setting in Bugzilla. Some installations may not want the reporter to have authority to mark a post off-topic since they could potentially use it to hide useful arguments against fixing the bug. III. All bugzilla users would have the option of A) displaying as normal, B) hiding or C) changing the display (such as the background color) of all posts marked "off-topic". Note: This should not be interpreted as a request to allow users in general to rate the insightfulness, etc. of a post (ala slashdot). This bug is for a single flag on each post that says whether or not that post is off-topic. Reproducible: Always Steps to Reproduce:
Isn't this a dupe of bug 42585?
Yeah, this is basically a good idea, but it's basically a duplicate of bug 283695, which should allow arbitrary marking of comments. *** This bug has been marked as a duplicate of 283695 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.