Global uniqueness requirement for project name results in frustrating UX
As a user
I want to create new projects
so that I can organize my services
Currently, the Aiven platform requires the project name to be unique across the entire Aiven platform and all its users. This can lead to an extremely frustrating user experience because the user has no clue what would project name might not have already been taken.
Project names should simply be unique per organization, at least as perceived by the user. Namespacing projects to the organization would be the obvious solution but another option might be to have separate project names and project IDs. The project ID could be unique across the platform by having some or all of it be auto-generated, while the user-defined project name helps the user identify and organize their projects.
AdminPeter Kim
(Senior Solution Architect, Aiven.io)
shared this idea
