-
Suggestion
-
Resolution: Unresolved
N/A
[AX-704] Enhance Cloud Admin REST APIs to support dedicated 'marked for deletion' status for managed accounts
Component/s | Original: Admin API tokens/keys [ 54490 ] | |
Component/s | New: Org Management - Cloud Admin API keys [ 80136 ] | |
Key | Original: ACCESS-1913 | New: AX-704 |
Support reference count | Original: 4 | |
Description |
Original:
h3. Problem Definition
At the moment *Organizations* and *User management* REST API do not support a dedicated status indicating that a managed account is 'marked for deletion'. This makes it impossible to discern whether a managed account is 'deactivated' or 'marked for deletion' just based on *account_status* attribute value in response from API. h3. Suggestion Add support for 'marked for deletion' status to *account_status* attribute, and make it consistent between *Organizations* and *User management* REST API. h3. Known workaround Atlassian administration UI displays managed accounts that are 'marked for deletion' with a dedicated lozenge. |
New: N/A |
Project | Original: Atlassian Guard [ 18910 ] | New: Admin Experience [ 24210 ] |
Support reference count | Original: 3 | New: 4 |
Support reference count | Original: 2 | New: 3 |
Support reference count | Original: 1 | New: 2 |
Description |
Original:
h3. Problem Definition
At the moment *Organizations* and *User management* REST API do not support a dedicated status indicating that a managed account is 'marked for deletion'. This makes it impossible to discern whether a managed account is 'deactivated' or 'marked for deletion' just based on *account_status* attribute value in response from API. h3. Suggestion Add support for 'marked for deletion' status to *account_status* attribute. h3. Known workaround Atlassian administration UI displays managed accounts that are 'marked for deletion' with a dedicated lozenge. |
New:
h3. Problem Definition
At the moment *Organizations* and *User management* REST API do not support a dedicated status indicating that a managed account is 'marked for deletion'. This makes it impossible to discern whether a managed account is 'deactivated' or 'marked for deletion' just based on *account_status* attribute value in response from API. h3. Suggestion Add support for 'marked for deletion' status to *account_status* attribute, and make it consistent between *Organizations* and *User management* REST API. h3. Known workaround Atlassian administration UI displays managed accounts that are 'marked for deletion' with a dedicated lozenge. |
Labels | New: guard-s7 |
Support reference count | New: 1 |