-
Suggestion
-
Resolution: Unresolved
-
5
-
Issue Summary
If the following 2 conditions are met:
- a site is created by a user who is a managed account, and
- all the current site admins are unmanaged,
the "Discovered products" feature would:
- show no Admins, and
- Contact admins contain no email addresses in "mailto:"
This is an intentional behavior according to support.atlassian.com:
If your managed accounts are removed as organization admins, the product continues to appear as a Discovered product, but you won’t see any contact information under Admins.
Steps to Reproduce
- Login to Atlassian Cloud with a managed account
- Start a site
- Remove yourself from the site admins
- The organization admins will see a vacant list in Discovered products > Admins
Expected Results
There's room to improve:
- clarify the reason why the organization admins see no Admins, and
- contain the site creator's email addresses in "mailto:"
- show the site creator in the table (the CSV contains the creator's contact).
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
- is related to
-
- Gathering Interest
[ACCESS-1341] Contain the site creator in "mailto" when discovered products list no Admins
| Status | Original: Gathering Interest [ 11772 ] | New: Not Being Considered [ 11776 ] |
| Support reference count | Original: 4 | New: 5 |
| Labels | New: guard-s7 |
| Support reference count | Original: 3 | New: 4 |
| Support reference count | Original: 2 | New: 3 |
| Support reference count | New: 2 |
| Link | New: This issue is related to ACCESS-1232 [ ACCESS-1232 ] |
| Summary | Original: Contain the site creator instead when discovered products list no Admins | New: Contain the site creator in "mailto" when discovered products list no Admins |
| Description |
Original:
h3. Issue Summary
If the following 2 conditions are met: * a site is created by a user who is a managed account, and * all the current site admins are unmanaged, the "Discovered products" feature would: * show no *Admins*, and * *Contact admins* contain no email addresses in "mailto:" This is an intentional behavior as documented at [support.atlassian.com|https://support.atlassian.com/security-and-access-policies/docs/review-discovered-products/]: bq. If your managed accounts are removed as organization admins, the product continues to appear as a Discovered product, but you won’t see any contact information under Admins. h3. Steps to Reproduce # Login to Atlassian Cloud with a managed account # Start a site # Remove yourself from the site admins # The organization admins will see a vacant list in *Discovered products* > *Admins* h3. Expected Results There's room to improve: * clarify the reason why the organization admins see no Admins, and * contain the site creator's email addresses in "mailto:" * show the site creator in the table (the CSV contains the creator's contact). h3. Workaround Currently there is no known workaround for this behavior. A workaround will be added here when available |
New:
h3. Issue Summary
If the following 2 conditions are met: * a site is created by a user who is a managed account, and * all the current site admins are unmanaged, the "Discovered products" feature would: * show no *Admins*, and * *Contact admins* contain no email addresses in "mailto:" This is an intentional behavior according to [support.atlassian.com|https://support.atlassian.com/security-and-access-policies/docs/review-discovered-products/]: bq. If your managed accounts are removed as organization admins, the product continues to appear as a Discovered product, but you won’t see any contact information under Admins. h3. Steps to Reproduce # Login to Atlassian Cloud with a managed account # Start a site # Remove yourself from the site admins # The organization admins will see a vacant list in *Discovered products* > *Admins* h3. Expected Results There's room to improve: * clarify the reason why the organization admins see no Admins, and * contain the site creator's email addresses in "mailto:" * show the site creator in the table (the CSV contains the creator's contact). h3. Workaround Currently there is no known workaround for this behavior. A workaround will be added here when available |
We truly value your suggestion and the thought you've put into it. If this feature starts to resonate with more users, we'll definitely take it into account. For now, though, it's not on our implementation list. Thanks for your understanding and for being such an important part of our community!