No Notification Provided When Creating a New Org when Org Slug Already Exists

[ReneGreen27]

Problem Statement

When Creating a New Sentry Org or placing a Migration request, if the org already exists it would be a better user experience to have the user notified in some way that the org slug is already taken. Instead it seems by default we automatically create a org slug with an autogenerated "-tworandomcharacters" attached. For example:

Solution Brainstorm

Either have a popup on the org creation page letting them know this isn't available, email the user in the case of the migration request

Product Area

Settings

[getsantry]

Assigning to @getsentry/support for routing ⏲️

[getsantry]

Routing to @getsentry/product-owners-settings for triage ⏲️

[leeandher]

This is fair feedback, but I'd say there's a reasonable benefit to having as little friction as possible when it comes to creating a new organization. Especially since if they did every want to adjust the slug, they could after they've already created the organization.

Even though the 'ideal' slug is taken, it's shouldn't affect their usage of Sentry and it's not something they need to memorize (though if this isn't true, we prioritize fixing those areas!).