View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0004542 | mantisbt | bugtracker | public | 2004-09-14 04:54 | 2004-11-06 06:50 |
Reporter | romat | Assigned To | thraxisp | ||
Priority | normal | Severity | major | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Product Version | 0.19.0 | ||||
Fixed in Version | 0.19.1 | ||||
Summary | 0004542: 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; On view issue page updater has only "Monitor issue" button. There is no "Change Status To" button. | ||||
Tags | No tags attached. | ||||
Forgot about |
|
"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. |
|
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. |
|
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. |
|
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. |
|
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. |
|
With the following configuration it works as in 0.18.3: $g_update_bug_status_threshold = UPDATER; My fault, I did not know about list of obsolete variables. Thank you. |
|
I added status "Closed" to aalowed for reporters (today, in my tests) and now reporter can close own bugs in my config |
|
Fixed in CVS. Re-introduced $g_reopen_bug_threshold. |
|