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:

Settings & Permissions

Scenario 1: Repository Settings

As a repository owner, I can configure specific settings for my repositories. This includes defining access controls, setting default permissions, and adjusting other repository-specific options (like notifications, robot accounts) as needed and as exists in the current UI.

Scenario 2: Organization Permissions

As an organization administrator, I can manage the permissions and access control for all repositories within the organization. This involves setting default permissions for new repositories, managing team permissions, and overseeing user access levels.