View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0023087 | mantisbt | filters | public | 2017-07-06 17:42 | 2017-09-03 18:41 |
Reporter | psbarron | Assigned To | atrol | ||
Priority | normal | Severity | minor | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Product Version | 1.3.5 | ||||
Target Version | 2.6.0 | Fixed in Version | 2.6.0 | ||
Summary | 0023087: Removing "Report an issue" permission removes user from Monitoring filter dropdown | ||||
Description | I have set the Updater profile so that an Updater is not permitted to report an issue. (The specific use case is that an outside vendor has access to read and update existing issues but not create new ones.) Certain Updaters are also added as monitors on issues. | ||||
Steps To Reproduce |
| ||||
Additional Information | Expected Behavior: User should still appear on dropdown and be available to filter by | ||||
Tags | No tags attached. | ||||
I have no time to try myself at the moment. Could you check if changing filter_form_api.php around line 288 (latest 2.6.0 developer code) from
to
fixes the issue? For version 1.3.x it should be filter_api.php around line 3721 (latest 1.3.11 version) BTW, you really should not go on using 1.3.5 as there are serious security issues in it. |
|
@psbarron can you confirm that the proposed change fixes the issue? |
|
@atrol - For some reason I have not been able to add a note to this issue to update it. I've added it but it disappears. I even cloned this issue to a new report in the hopes that you would see my update, but that doesn't appear to be visible either. So let's try again... We made the suggested code change in our test environment running 2.4.0: it was successful and resolved the problem. We then upgraded our production environment to 1.3.11 as you recommended and made the second code change there. Unfortunately, that did not work. When we clicked on the Monitor By filter we received an error message in the field that read (as best I can remember at this point) "Error: Bed Request". Any further suggestions would be appreciated. Thanks. |
|
There is a small difference in 1.3.x code. |
|
@atrol - We made the change in 1.3.11 and it has now resolved the problem. You can now mark this issue resolved. Thank you again! |
|
Fix will be included in versions >= 2.6.0 |
|