-
Suggestion
-
Resolution: Unresolved
-
None
Issue Summary
The Reporting Lines panel on a user profile is not visible to users who have access to the site, but whose accounts are not managed by the organization owning the site https://support.atlassian.com/user-management/docs/what-are-managed-accounts
Steps to Reproduce
- Create an account with a managed account from organisation 1 (user 1)
- Create an account with a managed account from organisation 2 (user 2)
- Have user 1 attempt to view the reporting line of user 2
Expected Results
User 1 can view the reporting line of user 2
Actual Results
User 2 cannot view the reporting line of user 2
Workaround
Currently there is no known workaround for this behaviour, a fix is required to update the permission checking
[ATLAS-150] Cross org reporting line permissions
| Description |
Original:
h3. Issue Summary
The Reporting Lines panel on a user profile is not visible to users who have access to the site, but whose accounts are not managed by the organization owning the site [https://support.atlassian.com/user-management/docs/what-are-managed-accounts|https://support.atlassian.com/user-management/docs/what-are-managed-accounts/] h3. Steps to Reproduce # Create an account with a managed account from organisation 1 (user 1) # Create an account with a managed account from organisation 2 (user 2) # Have user 1 attempt to view the reporting line of user 2 h3. Expected Results User 1 can view the reporting line of user 2 h3. Actual Results User 2 cannot view the reporting line of user 2 h3. Workaround Currently there is no known workaround for this behaviour, a fix is required to update the permission checking |
New:
h3. Issue Summary
The Reporting Lines panel on a user profile is not visible to users who have access to the site, but whose accounts are not managed by the organization owning the site [https://support.atlassian.com/user-management/docs/what-are-managed-accounts|https://support.atlassian.com/user-management/docs/what-are-managed-accounts/] h3. !https://downloads.intercomcdn.com/i/o/647142415/bff4c779bf7ba7aa08e3654f/177bbdb0-d236-4cf7-900e-dc108292b44a.png?expires=1739918700&signature=f0d49972d75df7c669cfb0cbca43bf6c8617515012396cdb7338c5778feaccd0&req=ciQgF818mYBaFb4f3HP0gBtpru1jaD4wpxNpvqJsdB8RbPdpWLTqZIlCVyvG%0AA7TowVdT9k6saVS%2B1A%3D%3D%0A|width=530,height=398! h3. Steps to Reproduce # Create an account with a managed account from organisation 1 (user 1) # Create an account with a managed account from organisation 2 (user 2) # Have user 1 attempt to view the reporting line of user 2 h3. Expected Results User 1 can view the reporting line of user 2 h3. Actual Results User 2 cannot view the reporting line of user 2 h3. Workaround Currently there is no known workaround for this behaviour, a fix is required to update the permission checking |
| Attachment | Original: image-2025-02-18-16-49-12-432.png [ 484754 ] |
| Description |
Original:
h3. Issue Summary
The Reporting Lines panel on a user profile !image-2025-02-18-16-49-12-432.png! is not visible to users who have access to the site, but whose accounts are not managed by the organization owning the site [https://support.atlassian.com/user-management/docs/what-are-managed-accounts|https://support.atlassian.com/user-management/docs/what-are-managed-accounts/] h3. Steps to Reproduce # Create an account with a managed account from organisation 1 (user 1) # Create an account with a managed account from organisation 2 (user 2) # Have user 1 attempt to view the reporting line of user 2 h3. Expected Results User 1 can view the reporting line of user 2 h3. Actual Results User 2 cannot view the reporting line of user 2 h3. Workaround Currently there is no known workaround for this behaviour, a fix is required to update the permission checking |
New:
h3. Issue Summary
The Reporting Lines panel on a user profile is not visible to users who have access to the site, but whose accounts are not managed by the organization owning the site [https://support.atlassian.com/user-management/docs/what-are-managed-accounts|https://support.atlassian.com/user-management/docs/what-are-managed-accounts/] h3. Steps to Reproduce # Create an account with a managed account from organisation 1 (user 1) # Create an account with a managed account from organisation 2 (user 2) # Have user 1 attempt to view the reporting line of user 2 h3. Expected Results User 1 can view the reporting line of user 2 h3. Actual Results User 2 cannot view the reporting line of user 2 h3. Workaround Currently there is no known workaround for this behaviour, a fix is required to update the permission checking |
| Description |
Original:
h3. Issue Summary
A user with a managed account from one organisation cannot view the reporting lines of a user with a managed account from a different organisation despite having read access. h3. Steps to Reproduce # Create an account with a managed account from organisation 1 (user 1) # Create an account with a managed account from organisation 2 (user 2) # Have user 1 attempt to view the reporting line of user 2 h3. Expected Results User 1 can view the reporting line of user 2 h3. Actual Results User 2 cannot view the reporting line of user 2 h3. Workaround Currently there is no known workaround for this behaviour, a fix is required to update the permission checking |
New:
h3. Issue Summary
The Reporting Lines panel on a user profile !image-2025-02-18-16-49-12-432.png! is not visible to users who have access to the site, but whose accounts are not managed by the organization owning the site [https://support.atlassian.com/user-management/docs/what-are-managed-accounts|https://support.atlassian.com/user-management/docs/what-are-managed-accounts/] h3. Steps to Reproduce # Create an account with a managed account from organisation 1 (user 1) # Create an account with a managed account from organisation 2 (user 2) # Have user 1 attempt to view the reporting line of user 2 h3. Expected Results User 1 can view the reporting line of user 2 h3. Actual Results User 2 cannot view the reporting line of user 2 h3. Workaround Currently there is no known workaround for this behaviour, a fix is required to update the permission checking |
| Attachment | New: image-2025-02-18-16-49-12-432.png [ 484754 ] |