Mantis Logo
Mantis Manual
Manual
Page Descriptions

Login page
Main page
View Bugs page
Bug View Simple page
Bug View Advanced page
Bug Change Status page
Bug Update Simple page
Bug Update Advanced page
My Account Page
System Management Pages
Monitor Bug
Reopen Bug
Delete Bug
Close Bug
Assign to Me
Resolve Bug
News Syndication


Partner Links


Resolve Bug
Last Modified: April 17, 2005 20:04PM
(Any)
Description

This option on the View Bugs page allows you to resolve the bug. It will lead you to a page where you can set the resolution state and a duplicate id (if applicable). After choosing that the user can choose to enter a bugnote detailing the reason for the closure. The bug is then set to the Resolved state. The reporter should check off on the bug by using the Close Bug button.

User Contributed Notes
Resolve Bug
Add Notes About Notes
marc@amir-tahmasseb.net
03-Dec-2003 2:41
#30
Actualy, when we resolve a bug, it is not possible to say in which version the bug is resolved!
pascalATkuczynski.nomDOTfr
09-Feb-2004 10:48
#66
in fact, we are happy if this version already exists!
I would like to say "this bug is resolved for <target version>"
m.van.hunnikREMOVE@SPaMplanet.nl
01-Apr-2004 14:19
#100
We are using Mantis version 0.18.2.
When a bug has the Status Resolved then the Reporter of this bug does not have the option Close available, only Reopen and Monitor.
My preference would be that the Reporter could also add a bugnote to a Resolved bug.
cdeady@aimltd.co.uk
22-Apr-2004 5:04
#117
Hi

I've worked through the process flow for resolving defects and I think it needs re-working. I'm in the process of modifying MantisBT for internal use accordingly.

The issues that I have observed are:
 - In the resolved list, there is the option "Open". While new defects have the resolved state of "Open", I cannot see a need for resolved defects to be set to status "Open". The resolution state of "Open" should therefore be hidden from the drop-down on the Resolve Bug page.

 - "Reopened" is not a resolution state, it is a progress state. If something is reopened, that indicates further work is required. However setting Resolved to "Reopened" places the bug in the "Resolved" state where the user will then need to manually reopen it even though they just told the system that the bug is reopened (confused yet?)

 - I have replaced the text "Resolved" in the Status list to "Pass", because we ultimately "Pass", "Fail" or "Reject" defects. However the resolved states of "fixed" and "not a bug" both set the status to "Resolved" (Pass). There needs to be a differential here - "Fixed" defects are "Resolved by having passed testing", but "not a bug" defects are "Resolved by having been rejected". There are other odd combinations possible here as well.

Hope that helps!
Regards
-Colin
cdeady@aimltd.co.uk
22-Apr-2004 5:59
#119
Hi again

I have also just noticed that it is possible to close a defect which has a resolved state of "open" or "reopened". This should generated a warning message to the user: "You should resolve a defect before closing it."

Please feel free to send me an email if you would like a hand with pinning down the process flow for resolving defects.
cdeady@aimltd.co.uk
22-Apr-2004 6:29
#120
Hi again

Apologies for lots of separate messages - there doesn't appear to be a way to edit my existing messages.

In my modified MantisBT I have successfully prevented users from closing bugs that are at state open or reopened with the following.

1) In file: bug_close_age.php

Insert directly below access_ensure_can_close_bug( $f_bug_id );

:

# prevent defects that are resolution "open" or "reopened" from being closed
if ( bug_get_field( $f_bug_id, 'resolution' ) == "10" or bug_get_field( $f_bug_id, 'resolution' ) == "30" ) {
   error_parameters( $f_bug_id );
   trigger_error( ERROR_BUG_CANNOT_CLOSE, ERROR );
}

2) In strings_english.txt (or your preferred language)

Insert:

$MANTIS_ERROR[ERROR_BUG_CANNOT_CLOSE] = 'Defects that are open or have been reopened cannot be closed until they are resolved';


3) In custom_constantinc.php

Insert:

# extra error when trying to close an unresolved defect
define( 'ERROR_BUG_CANNOT_CLOSE', 1101 );

Hope that helps!

Regards
-Colin
mulrich@bctNO-techSPAMogy.com
26-Apr-2004 8:11
#124
We applied the patch of cdeady@aimltd. It works really fine
and we think it should be part of the distribution...
idesouza@ipnetfusion.com
28-May-2004 10:02
#145
Hi, I really like your product. Its very well designed and stable.

I would like to ask, is there anyway I can avoid when clicking on the resolve button on the bug viewing screen, to NOT change the owner to me. I would like to say whether the bug should be place in resolved status without changing the current owner to myself, hence give credit to the developer who actually fixed the bug.

Thanks, Ian
dcantor@i-siglo21.com
11-Jun-2005 19:57
#465
Is there a way to update the change log page automatically when you resolve a bug in a given version? Despite of you can configure the versions in the project admin page, when you resolve a bug there is no indication (drop down box) for add the version in what the bug was resolved, and it does not link with change log page.
mantis_user@mailinator.com
26-May-2006 14:29
#1091
Is there a way to require that a user enter a note before resolving or closing an issue? It would be nice to be able to set "Add Note" to a required field. Thanks.
opshelpdesk@onlinetravel.com
22-Jun-2006 10:42
#1146
hi,

our version of mantis needs an extra drop down option when resolving a bug. can we do this ourselves?
opshelpdesk@onlinetravel.com
06-Jul-2006 10:44
#1180
can anyone help with this?

opshelpdesk@onlinetravel.com
22-Jun-2006 10:42 #1146
 
hi,

our version of mantis needs an extra drop down option when resolving a bug. can we do this ourselves?
 
Add Notes About Notes
Last updated: Wed, 23 Jul 2008 - 15:37:14

Mantis @ SourceForge