View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0015466||mantisbt||bugtracker||public||2013-02-06 08:07||2020-03-15 15:23|
|Target Version||2.24.0||Fixed in Version||2.24.0|
|Summary||0015466: Reporter can't see an issue they have been made a monitor of|
I have a reporter who has access to a private project, but $g_limit_reporters is set true so normally they can only see their own issues.
However I have set $g_reminder_receive_threshold = REPORTER so I can make them monitor an issue. However they cannot see this issue, so I presume that limit_reporters overrides the fact they have been made a monitor of an issue.
Is this expected operation - because it is a nice feature to selectively allow reporters to see issues raised by others (such as developers).
|Tags||No tags attached.|
I don't think this is a duplicate.
This one wants access for reporters to issues they did not report themselves although setting $g_limit_reporters = ON;
0005702 wants access to private issues for users without having $g_private_bug_threshold
I can confirm that I expect the same behavior as timdavey1. I also reproduce this issue.
Re-reading your note 0015466:0035154, I still feel it's a duplicate, i.e. the requirement would be satisfied by granting monitoring users visibility to the bug (disregarding $g_limit_reporters in this case). Let me know your thoughts.
I still think what I wrote in 0015466:0035154
The current issue is about a user who can't access an issue where he is added to the monitoring list because
Of course, both issues are fixed if you override both checks by granting monitoring users visibility to the issue.
This is what I meant actually...
MantisBT: master 97d6c385
|Implement limited view for monitored issues
The user that has a limited view now can also see the issues he is
|mod - core/access_api.php||Diff File|
|mod - core/classes/BugFilterQuery.class.php||Diff File|