Closed Bug 562920 Opened 16 years ago Closed 16 years ago

Tagging comments as bug/todo, fixed, verified, question, answer, split

Categories

(Bugzilla :: User Interface, enhancement)

3.0.4
x86
Linux
enhancement
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 283695

People

(Reporter: dale.forester, Unassigned)

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US) AppleWebKit/533.6 (KHTML, like Gecko) Chrome/5.0.380.0 Safari/533.6 Build Identifier: 3.0.4 We have a modified version of Bugzilla 3.0.4 where you can tag specific comments as bugs or todos (also auto-reopens a non-open bug) which can then be tagged as fixed and then be tagged as verified. I know some will find this odd but others may like thinking about it as new bugs vs new comments being like new processes vs new threads. It's very heavy to create a new bug compared to just commenting and reopening the same bug with a comment. This is all client-side javascript. Nothing interacts with the database. It is only meant to improve comprehension and organization and trackability while moving through the design, development, and QA stages of a particular bug. We can also tag a comment as a question which can then be answered. Comments can be tagged as split by which you indicate that its content has moved to another location (as indicated in the comment that does the splitting). Tags appear in the comment header line like this: ------- Comment #118 From John Doe 2010-04-29 20:04:54 - [Reply] [Bug] [Fixed] [Verified] ------- Each tag has a color attempting to match bugzilla's typical colors for the same meaning.. Bug/TODO are red. Fixed is orange. Verified is green. Hovering over a tag will indicate what comment made the tag. Clicking the tag will take you directly to the comment that made the tag also block highlighting the comment text with a similar color to the tag. The example comment header above may be caused by a sequence like: 1. New comment: > Bug: This is a bug because of x, y and z. 2. New comment: > #118: Fixed. > > Wups this bug was caused by a typo! 3. New comment: > #118: Verified > > X, y and z are now fixed. Finally, we have reports as links, in the "Related actions" boxes, that open in a new window and display the comments that are Unfixed, Unverified, or Open (includes unfixed, unverified and unanswered). This is a great way to make sure you've covered all your bases when deciding whether a bug is really fixed and verified. We find these improvements to be a vast gain in efficiency, organization and comprehension of the related bugs. It's also a great, quick visual way of running over a bug and seeing if there are any bugs, todos, or unfixed, unverified, or unanswered items left. We know that Mozilla would do a great job building and enhancing such a feature. I'd be happy to answer any questions about processes or quirks about using comment tagging. Reproducible: Always Steps to Reproduce: Enhancement. See details. Actual Results: Enhancement. See details. Expected Results: Enhancement. See details. Enhancement. See details.
Version: unspecified → 3.0.4
Thanks for the suggestion! This is pretty much a duplicate of bug 283695. (I just fixed the summary of that bug to make it clearer that it's a duplicate.)
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
#1: Ah, looks good, great to hear that.
You need to log in before you can comment on or make changes to this bug.