resolving a bug using mantis

Get help from other users here.

Moderators: Developer, Contributor

Post Reply
mechamecha
Posts: 2
Joined: 21 Oct 2008, 20:53

resolving a bug using mantis

Post by mechamecha »

hello,
I'm new to mantis, but not to bug tracking software.

in the bug tracking software i've used in the past, resolving a bug and marking it fixed would send the bug back to the qa tester for regression. once the qa tester had regressed the bug, he would have the option to mark the bug fixed are not fixed. if the bug was fixed, it would get sent to the qa lead who would update the bug's status to closed. if it was not fixed, it would be sent back to the developer. this is the workflow i am most familiar with.

does mantis operate like this work flow? i've notice updating a bug to resolved does not send it back to the reporter. is there a way to get it sent back to the reporter?
perhaps mantis works under a different work flow...if that were the case, i would appreciate someone outlining it for me or posting a link. i've searched the manual and the mantis site, but i havent found any info on this.

thanks!
jb_mantis
Posts: 63
Joined: 14 Oct 2008, 12:41
Location: Columbus, Ohio, USA

Re: resolving a bug using mantis

Post by jb_mantis »

Here is how to accomplish it in Mantis.

If your QA Testers are the issue Reporters, do this:
Under the Manage -> Manage Configuration -> Workflow Thresholds page, enable the option "Allow Reporter to close Issue".
If your QA Testers are not the Reporters, you need to either give them Developer access or do something like give them Updater access and lower the values for who can handle (be assigned) an issue and maybe some other options found on the same page mentioned above.

When a bug is resolved, have the developer click the "Update Issue button" and change it's resolution to whatever is appropriate and change the status to resolved.
If the QA Testers have developer access and can be assigned issues, the developer could also assign the issue to them at this time.
If the QA Tester has developer access, they can re-test the bug and if it passes, assign the issue to the QA Lead, assuming they have developer or above access, and if it fails, reassign it to the developer and change status back to something between feedback and assigned and change the resolution to open or reopened.
If the QA Tester is not a developer but is the reporter, they should get an email notification about the status change and they can come and review the issue and close it if it is fixed or reopen it if it is not, although closing it would bypass the QA Lead review.
-Joe
Mantis Version: 1.1.2
Disclaimer: Answers are based on the Mantis version above and may be inaccurate for newer/older versions which may have different configuration options and/or functionality.
olegos
Posts: 72
Joined: 12 Mar 2007, 20:24

Re: resolving a bug using mantis

Post by olegos »

I've added a custom Verified status between Resolved and Closed to support exactly the workflow you're talking about, by following these instructions. You may control who is allowed to perform what transition, and who gets e-mail notifications for each transition. (I allow Resolved -> Verified transition by any Reporter, and Reporters are also allowed to Reopen issues if verification fails.)
changhua0313
Posts: 1
Joined: 21 Jan 2009, 16:12

Re: resolving a bug using mantis

Post by changhua0313 »

Dear jb_mantis,

I've enabled the option "Allow Reporter to close Issue". But the reporter can not find any action link or button to close the resolved bug he/she reported. Would you like to tell me where the reporter can close the bug or anything I missed?


Mantis: 1.1.6
PHP:5.2.8
database: MySQL 5.0.22

All mantis configurations are default values except "Allow Reporter to close Issue" is set to ON.

Any hint is appreciated. Thank you every much.
olegos
Posts: 72
Joined: 12 Mar 2007, 20:24

Re: resolving a bug using mantis

Post by olegos »

See bug #10066. You probably have bugs becoming read-only in Resolved state, so most changes are prohibited.
Post Reply