-
Suggestion
-
Resolution: Unresolved
-
None
-
1
-
Problem
When using a plan with restricted permission scheme, a user with the proper access to the plan but without the global Browse User permission is not able to add other users to the permission section, even when providing the exact e-mail of the user:
Key notes
- There are no official requirements to have Browse Users permission to be able to use Advanced Roadmaps.
Suggested Solution
Provide the ability to add users in the menu from the screenshot by typing out the exact e-mail or username, even without the auto-complete functionality, making sure the user has the proper permissions for Advanced Roadmaps and providing a generic error message in case the user is not found or doesn't have the proper permission.
- Making sure the message is generic is important so it is not possible to "test" and see if the user exists in the user base for Jira.
Why This Is Important
This functionality is key to allow the proper maintenance of Advanced Roadmaps in a multi-tenancy scenario where you have multiple niches that should not have any visibility of other niches besides what they have been given permission.
Workaround
It is still possible to add groups which the user belongs too.
A group could be created containing the admins or list of viewers or admins for a plan.
- relates to
-
JSWSERVER-21343 Unable to assign issues on Advanced Roadmaps without global Browse Users permission
-
- Gathering Impact
-
- is related to
-
JPO-19811 Failed to load
- links to
- mentioned in
-
Page Failed to load
[JSWSERVER-21328] Provide ability to update Plan-specific permissions in Advanced Roadmaps without global Browse User
| Labels | Original: DC-150 pse-request | New: DC-150 pse-request ril |
| Remote Link | New: This issue links to "Internal ticket (Web Link)" [ 979370 ] |
| Remote Link | New: This issue links to "Page (Confluence)" [ 752125 ] |
| UIS | New: 1 |
| Labels | Original: pse-request | New: DC-150 pse-request |
| Description |
Original:
h3. Problem
When using a plan with restricted permission scheme, a user with the proper access to the plan but without the global Browse User permission is not able to add other users to the permission section, even when providing the exact e-mail of the user: !image-2022-04-21-16-26-11-447.png|width=464,height=420! *Key notes* * There are no official requirements to have *Browse Users* permission to be able to use Advanced Roadmaps. h3. Suggested Solution Provide the ability to add users in the menu from the screenshot by typing out the exact e-mail or username, even without the auto-complete functionality, making sure the user has the proper permissions for Advanced Roadmaps and providing a generic error message in case the user is not found or doesn't have the proper permission. * Making sure the message is generic is important so it is not possible to "test" and see if the user exists in the user base for Jira. h3. Why This Is Important This functionality is key to allow the proper maintenance of Advanced Roadmaps in a multi-tenancy scenario where you have multiple niches that should not have any visibility of other niches besides what they have been given permission. h3. Workaround It is still possible to add groups which the user belongs too. A group could be created containing the admins or list of viewers for a plan and the user can add members to said group or add the entire group while on the permission section. |
New:
h3. Problem
When using a plan with restricted permission scheme, a user with the proper access to the plan but without the global Browse User permission is not able to add other users to the permission section, even when providing the exact e-mail of the user: !image-2022-04-21-16-26-11-447.png|width=464,height=420! *Key notes* * There are no official requirements to have *Browse Users* permission to be able to use Advanced Roadmaps. h3. Suggested Solution Provide the ability to add users in the menu from the screenshot by typing out the exact e-mail or username, even without the auto-complete functionality, making sure the user has the proper permissions for Advanced Roadmaps and providing a generic error message in case the user is not found or doesn't have the proper permission. * Making sure the message is generic is important so it is not possible to "test" and see if the user exists in the user base for Jira. h3. Why This Is Important This functionality is key to allow the proper maintenance of Advanced Roadmaps in a multi-tenancy scenario where you have multiple niches that should not have any visibility of other niches besides what they have been given permission. h3. Workaround It is still possible to add groups which the user belongs too. A group could be created containing the admins or list of viewers or admins for a plan. |
| Description |
Original:
h3. Problem
When using a plan with restricted permission scheme, a user with the proper access to the plan but without the global Browse User permission is not able to add other users to the permission section, even when providing the exact e-mail of the user: !image-2022-04-21-16-26-11-447.png|width=464,height=420! h3. Suggested Solution Provide the ability to add users in the menu from the screenshot, even without the auto-complete functionality, making sure the user has the proper permissions for Advanced Roadmaps and providing a generic error message in case the user is not found or doesn't have the proper permission. * Making sure the message is generic is important so it is not possible to "test" and see if the user exists in the user base for Jira. h3. Why This Is Important This functionality is key to allow the proper maintenance of Advanced Roadmaps in a multi-tenancy scenario where you have multiple niches that should not have any visibility of other niches besides what they have been given permission. h3. Workaround It is still possible to add groups which the user belongs too. A group could be created containing the admins or list of viewers for a plan and the user can add members to said group or add the entire group while on the permission section. |
New:
h3. Problem
When using a plan with restricted permission scheme, a user with the proper access to the plan but without the global Browse User permission is not able to add other users to the permission section, even when providing the exact e-mail of the user: !image-2022-04-21-16-26-11-447.png|width=464,height=420! *Key notes* * There are no official requirements to have *Browse Users* permission to be able to use Advanced Roadmaps. h3. Suggested Solution Provide the ability to add users in the menu from the screenshot by typing out the exact e-mail or username, even without the auto-complete functionality, making sure the user has the proper permissions for Advanced Roadmaps and providing a generic error message in case the user is not found or doesn't have the proper permission. * Making sure the message is generic is important so it is not possible to "test" and see if the user exists in the user base for Jira. h3. Why This Is Important This functionality is key to allow the proper maintenance of Advanced Roadmaps in a multi-tenancy scenario where you have multiple niches that should not have any visibility of other niches besides what they have been given permission. h3. Workaround It is still possible to add groups which the user belongs too. A group could be created containing the admins or list of viewers for a plan and the user can add members to said group or add the entire group while on the permission section. |
| Remote Link | New: This issue links to "JPO-19811 (JDOG)" [ 639062 ] |
| Link | New: This issue relates to JSWSERVER-21343 [ JSWSERVER-21343 ] |
| Labels | New: pse-request |