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.

Epic Goal:

Enhance the performance and effectiveness of the Quay UI at scale  by building core functionality with all of the functionalities that exist on Quay.io today. 

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: 

• Default Permissions Configuration:
  • Users can access a dedicated section in the UI to configure default permissions settings for repositories, users, or organizations.
• Granular Permission Levels:
  • UI allows users to define default permission levels (e.g., read, write, admin) for different user roles (e.g., members, collaborators) and entities (e.g., repositories, organizations).