Mission:

To achieve core functionality in the UI and migrate more screens to console.redhat to win new customers, encourage existing customers to upgrade to a paid plan, increase retention of current paid users, and foster future Quay business through creating partnerships across the Red Hat ecosystem.

Why is this important?

Supporting core UI functionality and performance at scale is crucial for providing a seamless user experience while providing large paying  customers with large content the functionality required to do business at scale.  Achieving UI parity with Quay.io ensures that users can utilize all functionalities without limitations. Addressing critical UI bugs enhances stability and usability, resulting in higher customer satisfaction and enhance their effectiveness on the Quay UI. 

Acceptance Criteria:

Teams and Membership

Scenario 1: Create a New Team

As a Quay user, I can create a new team within an organization. I can specify the team name, description, and members during the creation process. I can manage membership, add or remove users, and assign roles to team members.

Scenario 2: Modify Team Membership

As a team administrator, I can manage team membership efficiently. I should be able to add new users, remove existing members, and update their roles within the team. This will allow me to ensure that the right individuals have access to the team's resources and repositories.