Add release email workflow specific to unverified secondary email address
Request for comments
Need
Reviewing the workflow to release an unverified email address from a GitLab.com account is confusing. Following the implementation of gitlab-org/gitlab#352514 (closed) , primary email unverified leads to account been deleted after few days. Waiting on gitlab-org/gitlab#367823 (closed) to be implemented to automatically release unverified secondary email we need to update the workflow.
Approach
According to the current workflow introduction we can use the process below for unverified secondary email for free users. But is doesn't defined activity (is it 2years old like for namesquatting request ? ) / the workflow seems to be created for primary email address release only
Benefit
Clarify, simplify! I checked all the tickets listed in the issue related to secondary email release but in most cases Support help the user user to regain access to their account (so they can release themselves), and only one release of email by Support.
Possible simplified workflow
This workflow should be use only to release unverified secondary email address:
- Confirmed the email addressed is an unverified secondary email address.
- If the ticket was submitted via the ZD form, please ask email verification.
- Once the user has replied to confirm they own the email address, remove the secondary email from the account
- Add an Admin Note to the user’s account: 2024-01-30 | removed secondary unverified email address from the account
john@xyz.com
| https://gitlab.zendesk.com/agent/tickets/ - Reply to the user, their email address is now release and they can use it to create a new account.
- Comment on this feature request