avatar image

Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
  • Saturday July 20, 2024, 1:47 am
  • Proudly celebrating 15+ years online.
  • Donate now to become a lifetime supporting member of the site and get a non-expiring license key for all of our programs.
  • donate

Author Topic: Closing, updating, & resolving bugs w/Mantis bug tracker  (Read 7500 times)


  • Supporting Member
  • Joined in 2006
  • **
  • Posts: 143
    • View Profile
    • Superticker's SU reviews about technology
    • Donate to Member
Closing, updating, & resolving bugs w/Mantis bug tracker
« on: September 19, 2006, 04:02 PM »
The Mantis manual explains that after a bug is marked resolved, the reporter should close it.  I have reporter-level access and I'm the reporter of a resolved bug, but I fail to see the Close button in my views window.  Is that because this bug-closing feature is not used here at DonationCoder?

I'm just asking.  I'm not suggesting this closing feature should be enabled here.  I see there's a button to reopen a resolved bug, so maybe the closing feature is unnecessary, and may never be used anyway.

There's no update button on my reporter-level view window.  Is that normal?  What if I want to modify my bug report later?  Should I just attach a note?

Some bugs I reported earlier are resolved now, but there's no resolved button available in the reporter-level views window.  Is that normal?  Is it only the programmer that marks the bug resolved, not the reporter?  If so, I guess he hasn't gotton around to doing that yet.  :-)


  • Review 2.0 Designer
  • Charter Member
  • Joined in 2005
  • ***
  • Posts: 2,739
    • View Profile
    • Donate to Member
Re: Closing, updating, & resolving bugs w/Mantis bug tracker
« Reply #1 on: September 29, 2006, 11:14 PM »
Bug tracking etiquette and convention always seems a little different from system to system and project to project. I haven't used the DC Mantis setup yet, but in general the assignee of the bug is the one who marks "resolved" and someone else tests and marks "closed". In a professional development situation someone else is formally verifying and/or regressing bugs, in which case it would be marked closed by whoever is doing the verification (not necessarily the original reporter). In this case the conventions may need adjusting unless the reporter can be counted on to verify the resolution and close it. I doubt anyone has time to be the official DC bug tester, so maybe closing bugs just won't happen normally.

In most bug trackers I've seen you can't usually update the original bug *text*, although you can sometimes change other stuff like version, priority, etc. This also depends on permissions. But in any case if you have mode to add the usual convention is to do so in a subsequent comment/note because then you maintain the history of the bug. This is precisely what the note feature is for.

Finally, in my experience it is the developer that will mark something as resolved and specify a resolution/reason. This gives them a function to notify others when it has been taken care of on their end as well as the ability to mark as resolved bugs they decide not to fix ("featured"), feature requests they decide not to implement, etc. Bug *closure* is the step taken after resolution, and indicates that the bug fix has been tested and verified.

- Oshyan