View Issue Details

IDProjectCategoryView StatusLast Update
0004542mantisbtbugtrackerpublic2004-11-06 06:50
Reporterromat Assigned Tothraxisp  
PrioritynormalSeveritymajorReproducibilityalways
Status closedResolutionfixed 
Product Version0.19.0 
Fixed in Version0.19.1 
Summary0004542: Updater cannot reopen issue and cannot close his own issues
Description

With the following setting in config_inc.php it worked in Mantis 0.18.3, but does not work in 0.19.0:

$g_close_bug_threshold = MANAGER;
$g_allow_reporter_close = ON;
$g_reopen_bug_threshold = UPDATER;

On view issue page updater has only "Monitor issue" button. There is no "Change Status To" button.

TagsNo tags attached.

Relationships

child of 0004297 closedvboctor Mantis 0.19.1 release 

Activities

Wanderer

Wanderer

2004-09-14 05:43

developer   ~0007556

Forgot about
$g_update_bug_status_threshold = UPDATER;
but AFAIK possibility "close own" was really lost - at least I can't get it
Reopening in my installation possible even for reporters (for own bugs)

bpfennig

bpfennig

2004-09-14 06:15

reporter   ~0007557

"handle reporter can reopen" and "handle reporter can close" in function "html_button_bug_change_status" should use function "access_can_reopen_bug" and function "access_can_close_bug" to grant access for reopen and close.

romat

romat

2004-09-14 06:40

reporter   ~0007558

Yes, Mantis 0.19.0 new settings ($g_update_bug_status_threshold and $g_set_status_threshold) solved one part of this problem. $g_close_bug_threshold and $g_reopen_bug_threshold are now obsolete. It should be more clear in 0.19.0 list of changes.

It looks that $g_allow_reporter_close has no effect.

thraxisp

thraxisp

2004-09-14 07:42

reporter   ~0007560

If you run the admin check (admin/check.php), close_bug_threshold and reopen_bug_threshold are marked as obsolete (replaced, as you noted, by set_status_threshold).

There was a bug fix late in 0.19.0 to add back the allowreporter(close|reopen) functionality. A reporter should see close and reopen in the change status to: list if the issue is resolved.

bpfennig

bpfennig

2004-09-14 07:54

reporter   ~0007562

But "reopened" is not a status - it's a resolution, so reopened couldn't be used in set_status_threshold.

I think the problem caused by what I've posted in my last note. Not only the reporter who reported the bug should be able to reopen the bug. It should be possible to configure who are able to reopen the bug.

thraxisp

thraxisp

2004-09-14 08:08

reporter   ~0007563

I agree that reopen is cryptic.

$g_set_status_threshold[$g_bug_reopen_status] controls who else may re-open the bug. I'm beginning to think that we should make this explicit and bring back a re-open threshold.

I'll mark this for 0.19.1 to re-introduce the reopen threshold.

romat

romat

2004-09-14 08:19

reporter   ~0007566

With the following configuration it works as in 0.18.3:

$g_update_bug_status_threshold = UPDATER;
$g_set_status_threshold = array(CLOSED => MANAGER );
$g_allow_reporter_close = ON;

My fault, I did not know about list of obsolete variables. Thank you.

Wanderer

Wanderer

2004-09-14 09:10

developer   ~0007569

I added status "Closed" to aalowed for reporters (today, in my tests) and now reporter can close own bugs in my config

thraxisp

thraxisp

2004-09-23 16:27

reporter   ~0007723

Fixed in CVS.

Re-introduced $g_reopen_bug_threshold.