-
Suggestion
-
Resolution: Unresolved
-
1
-
Problem Definition
The "transfer list" currently shows a static list of prerequisites that need to be met before the "Transfer products" button is clickable. The "user provisioning" link on that checklist directs admins to the incorrect user provisioning directory if provisioning is not configured.
Suggested Solution
- Update the link to point to: https://admin.atlassian.com/o/<org_id>/idp
- The solution could also be to remove the legacy/old user provisioning configuration page
Why this is important
- Admins are directed to the incorrect page where provisioning is configured this is confusing because if an admin tries to configure a new directory via the linked page, then they will get a 403 response
Workaround
No known workarounds. A workaround will be added if one is found
- is cloned from
-
ACCESS-1316 Product transfer: Update the transfer checklist to be dynamic
- Gathering Interest
[ACCESS-1419] Product transfer: Link to "user provisioning" in transfer checklist needs to be updated
Labels | New: guard-s7 |
Description |
Original:
h3. Problem Definition
The "transfer list" currently shows a static list of prerequisites that need to be met before the "Transfer products" button is clickable h3. Suggested Solution * Make the list dynamic - when certain prerequisites are met, remove that item from the list * Alternatively, each item can receive a check mark(or strikethrough tag) once that particular requirement has been satisfied h3. Why this is important * Easier for admins to see what they need to do to be able to transfer the linked sites to another org. * The "Delete organization" experience displays a dynamic list of requirements !Screenshot 2022-09-08 at 10.24.32.png|thumbnail! h3. Workaround No known workarounds. A workaround will be added if one is found |
New:
h3. Problem Definition
The "transfer list" currently shows a static list of prerequisites that need to be met before the "Transfer products" button is clickable. The "user provisioning" link on that checklist directs admins to the incorrect user provisioning directory _if_ provisioning is not configured. !Screenshot 2022-12-22 at 14.07.01.png|thumbnail! h3. Suggested Solution * Update the link to point to: https://admin.atlassian.com/o/<org_id>/idp * The solution could also be to remove the legacy/old user provisioning configuration page h3. Why this is important * Admins are directed to the incorrect page where provisioning is configured this is confusing because if an admin tries to configure a new directory via the linked page, then they will get a 403 response h3. Workaround No known workarounds. A workaround will be added if one is found |
Attachment | New: Screenshot 2022-12-22 at 14.07.01.png [ 432204 ] |
Link | New: This issue is cloned from ACCESS-1316 [ ACCESS-1316 ] |