Confirmed users
3,314
edits
BMO/comment tagging: Difference between revisions
→Automatic Collapsing of Comments: duplicate
(→Automatic Collapsing of Comments: duplicate) |
|||
| (9 intermediate revisions by 5 users not shown) | |||
| Line 3: | Line 3: | ||
A enhancement which allows you to tag individual comments with arbitrary strings has been deployed on [https://bugzilla.mozilla.org bugzilla.mozilla.org]. | A enhancement which allows you to tag individual comments with arbitrary strings has been deployed on [https://bugzilla.mozilla.org bugzilla.mozilla.org]. | ||
[[File: | [[File:Comment_spam.gif||Comment Tagging Spam]] | ||
Comment tags are saved immediately - you do not need to hit "Save Changes" but you do need to press Enter after selecting the tag from the popup. | |||
=== Comment Tagging Features === | === Comment Tagging Features === | ||
| Line 15: | Line 15: | ||
This allows obsolete or irrelevant comments to be hidden from the information stream. | This allows obsolete or irrelevant comments to be hidden from the information stream. | ||
Currently tagging a comment as '''spam''', '''obsolete''', '''me-too''', '''advocacy''', '''off-topic''', '''abuse''', '''abusive''', or '''typo''' will trigger this. | Currently tagging a comment as '''spam''', '''duplicate''', '''obsolete''', '''me-too''', '''advocacy''', '''off-topic''', '''offtopic''', '''abuse''', '''abusive''', '''admin''', or '''typo''' will trigger this. | ||
Please use the right tags when reporting comments that [https://bugzilla.mozilla.org/page.cgi?id=etiquette.html violate our etiquette policies] so that site admins can take the right actions and keep Bugzilla a friendly and spam-free place to report and track bugs. | |||
'''spam''': comments that look like someone's trying to game search results by adding links to unrelated sites to comments should be tagged as spam. Look out for comments of the form "I see this happening on my site too," as they may be spam and not additional information for a bug. | |||
'''off-topic''', '''offtopic''', '''me-too''', or '''advocacy''': "me too", "fix this ''now''!", "I can't believe this isn't important to Mozilla" and similar comments should be tagged with one of these. See our [https://bugzilla.mozilla.org/page.cgi?id=etiquette.html etiquette guide]. | |||
'''abuse''', '''abusive''', or '''admin''': Flames, threats, name-calling, and slurs are abuse, and should be marked as such so they are brought to the attention of an admin. | |||
'''duplicate''', '''obsolete''', and '''typo''' should only be use used to remove comments which are no longer relevant, contain outdated or incorrect information, or ones the author wishes to redact. | |||
Our response to violations of Bugzilla etiquette depends on the type of violation. We don't want to treat someone who is unaware of how conversations work to be marked as a spammer, and we don't want to go uninformed about abuse. | |||
==== Comment Grouping/Threading ==== | ==== Comment Grouping/Threading ==== | ||
| Line 30: | Line 42: | ||
For example: | For example: | ||
* tagging a comment with | * tagging a comment with “'''STR'''” (steps to reproduce) will help the QA team quickly find the information they need to verify the fix | ||
* writing a comment summarising a new feature and tagging it with | * writing a comment summarising a new feature and tagging it with “'''docs'''” will help the generation of documentation for MDN or similar | ||
==== Comment Tagging from Apps ==== | |||
Applications using our APIs can post tags to comments. | |||
===== Bugherder ===== | |||
The [https://bugherder.mozilla.org/ bugherder application] will post a comment on behalf of a user when they take an action: | |||
* The <code>bugherder</code> tag indicates that the comment is from bugherder | |||
* <code>landing</code>, <code>backout</code>, <code>uplift</code> describe the commit(s) being marked | |||
* The app also posts the link to the commit message, and sets the appropriate release status flags | |||
=== Implementation Notes === | === Implementation Notes === | ||