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:

Usage Logs

Scenarios:

• Monitor Team Activities: System administrators can monitor team-related activities, such as team creation, membership changes, and role assignments, through usage logs.
• Audit Tag History Actions: Security auditors can audit tag history actions, including tag creations, updates, and deletions, using the provided usage logs.
• Track Repository Label Changes: Repository owners can track changes to repository labels, including additions, modifications, and removals, via usage logs.
• Monitor Expiration Settings: DevOps engineers can monitor actions related to tag expiration settings, such as setting expiration dates or disabling expiration for specific tags, through usage logs