View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0022745||mantisbt||feature||public||2017-04-19 10:01||2017-04-21 02:51|
|Summary||0022745: Grant Access in VIEW mode (Read Only) 'skipping' user threshold|
I will try to explain why this feature can be useful presenting my current installation:
Some times user need to access an issue on a project he/she is not assigned, and this is not possible.
IMHO it will be a good thing if users can skip project authorization checks using a simple criteria like: all users with email in domain xxxxx.yy (where xxxxx.yy in my situation will be our company domain), can access issues no matter PROJECT VIES STATUS and/or ISSUE VIEW STATUS.
I've done a hack (not a good one) that implement this, but I think a better implementation will be useful.
Hope my explanation is not so confusing.
Thanks for this great product
|Tags||No tags attached.|
Is this 0022203 what you need?
First, thanks a lot for your quick answer. I'm sorry I was lazy enough to do not search before reporting.
Right now my hack does not allow this, user will <b>access with full rights</b>, this means he/she can change the issue, but this is not really a drawback (at least IMHO) because issue history will record actions and author.
Hope now is a little bit clear.
That means that another user sent him/her the issue number to have a look at the issue. Right?
Also related 0006758 where a user implemented access level driven by LDAP group.
Thanks again for your help.
Not really, the user can get the issue number when looking to commit logs on git, then IMHO is easier just get the number and put on the search box on mantis, than have th public share url.
My intention was to have something that require no configuration (I suppose if/when user groups will be supported may be this can be another solution).