View Issue Details

IDProjectCategoryView StatusLast Update
0004538mantisbtbugtrackerpublic2004-11-06 06:54
Reporterbpfennig Assigned Tothraxisp  
PrioritynormalSeveritymajorReproducibilityalways
Status closedResolutionfixed 
Product Version0.19.0 
Fixed in Version0.19.1 
Summary0004538: $g_bug_resolved_status_threshold doesn't work correctly with additional status
Description

I've add an additional status "To be tested", this status is set to $g_bug_resolved_status_threshold. So, if this status is changed, the Issue Tracker shows the right "bug_change_status_page" (the page for resolving a bug - so the user can set a resolution and so on).

All right at the moment - but sometimes a bug isn't a bug - so it has to be resolved (Status resolved) from status new or what ever. But then the "bug_change_status_page" doesn't allow to set the resolution, it's only possible to set the "fixed in version".

TagsNo tags attached.

Relationships

child of 0004297 closedvboctor Mantis 0.19.1 release 

Activities

thraxisp

thraxisp

2004-09-14 08:18

reporter   ~0007565

You are correct. The resolution box is only present when the status equals $g_bug_resolved_status_threshold.

I think that it should be >= $g_bug_resolved_status_threshold and < CLOSED.

bpfennig

bpfennig

2004-09-14 08:54

reporter   ~0007568

It would be nice if the admin can configure which fields are visible at the bug_change_status_page. This could solve another issue 0004440. But I think this was a major redesign.

thraxisp

thraxisp

2004-09-16 12:18

reporter   ~0007622

The longer term solution for what is visible where is the template system (ref 0004227).

thraxisp

thraxisp

2004-09-21 13:23

reporter   ~0007671

The original problem is fixed in CVS.

The bug_change_status_page will show the resolution for more status values.