Project:
| View Revisions: Issue #38758 | [ All Revisions ] [ Back to Issue ] | ||
| Summary | 0038758: having write access to a parent and one of its children orgs, sometimes it's not possible to read siblings of child one | ||
| Revision | 2018-06-14 16:38 by alostale | ||
| Description | Having an organization A, with at least 2 child nodes B and C and a role with write access to A and only one of its children (B or C):A / \ B C When logging with that role, organization C should be readable but not writable. But randomly organization C is not visible at all. |
||
| Revision | 2018-06-14 16:37 by alostale | ||
| Description | Having an organization A, with at least 2 child nodes B and C and a role with write access to A and only one of its children (B or C):A / \ B C When logging in with that role, organization C should be readable but not writable. But randomly organization C is not visible at all. |
||
| Revision | 2018-06-14 16:26 by alostale | ||
| Description | Having an organization A, with at list 2 child nodes B and C and a role with write access to A and only one of its children (B or C):A / \ B C When logging in with that role, organization C should be readable but not writable. But randomly organization C is not visible at all. |
||
| Revision | 2018-06-14 16:22 by alostale | ||
| Description | Having an organization A, with at list 2 child nodes B and C.A / \ B C |
||
| Revision | 2018-06-14 16:19 by alostale | ||
| Description | In case several organizations are defined as "Org Access" for a role, results produced by setReadableOrganizations method could be different | ||
| Copyright © 2000 - 2009 MantisBT Group |
 |