View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0023693||mantisbt||bugtracker||public||2017-12-04 00:58||2017-12-07 03:32|
|Status||resolved||Resolution||no change required|
|Target Version||Fixed in Version|
|Summary||0023693: User with reopen privilege cannot reopen read only issues|
As mentioned in the forum: https://www.mantisbt.org/forums/viewtopic.php?f=3&t=24875
This happen to user with privilege to reopen issues but not permitted to modify read only issues.
|Steps To Reproduce|
The user can click the reopen button and add the message before click reopen again.
I reproduced the error in v2.5.1 and v2.8.0
APPLICATION ERROR #1103
|Tags||No tags attached.|
Read-only means "not allowed to write / change anything".
Do you agree?
In my cause, I will like to let reporters reopen issue that happens again. In order to achieve that, I will also need to give them the capability to modify read-only issues for now. But some of the reporters will forget to reopen the issue after adding note on the issue that occurs again. This will keep the issue in closed status and be hidden by default.
I think a solution for that is requiring the reporter to reopen a read-only issue before they can add notes on it. By setting the reporter cannot modified read-only issues but is able to reopen it.
In Mantis administrator guide, it is said that "The bug becomes read/write again if re-opened".
Please don't quote parts of sentences as this changes the meaning.
The whole paragraph is
Could be rephrased to
So if I understand well, to reopen a bug a user should have an access level greater than or eqaul to reopen_bug_threshold AND update_readonly_bug_threshold. reopen_beg_thresheold alone is not enough. Is that right ?
Another approach that might work for you could be to change
|2017-12-04 00:58||Zipher||New Issue|
|2017-12-04 07:46||atrol||Status||new => feedback|
|2017-12-04 07:46||atrol||Note Added: 0058310|
|2017-12-05 05:08||Zipher||Note Added: 0058315|
|2017-12-05 05:08||Zipher||Status||feedback => new|
|2017-12-06 11:09||smeynieux||Note Added: 0058324|
|2017-12-06 12:44||atrol||Note Added: 0058325|
|2017-12-07 00:35||dregad||Note Added: 0058326|
|2017-12-07 03:24||smeynieux||Note Added: 0058331|
|2017-12-07 03:30||atrol||Note Added: 0058332|
|2017-12-07 03:31||atrol||Note Added: 0058333|
|2017-12-07 03:32||atrol||Assigned To||=> atrol|
|2017-12-07 03:32||atrol||Status||new => resolved|
|2017-12-07 03:32||atrol||Resolution||open => no change required|