Uploaded image for project: 'Project Quay'
  1. Project Quay
  2. PROJQUAY-6303

3.11 Core UI Features- RH Quay

XMLWordPrintable

    • Icon: Feature Feature
    • Resolution: Unresolved
    • Icon: Critical Critical
    • None
    • None
    • None
    • False
    • None
    • False
    • Not Selected
    • 28
    • 28% 28%
    • 0

      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.

      Summary:
      Introduce a series of significant enhancements to downstream Quay UI by the 3.11 release, aimed at improving user experience, performance, and functionality. Key deliverables include integrating Builds, Usage Logs, Notifications, OAuth, and the Super User Panel to complete the core UI and set the new UI as the default option. Being that Quay.io codebase are nearly identical these UI updates will also be applied with the exception of what's called out in 6346

      See slide deck for full roadmap:

      Description:
      As part of the 3.11 release, we are committed to enhancing the Quay user interface to provide our users with a more streamlined and feature-rich experience. This JIRA feature request encompasses multiple sub-tasks, each focused on a specific aspect of the Quay UI.

      Deliverables

      • New UI as Default:
           - Design and implement the new Quay UI as the default user interface.
           - Ensure a seamless transition for existing users, preserving their settings and configurations.
           - Conduct thorough testing to verify the new UI's functionality and performance as the default option.
      • Builds Integration:
           - Develop a robust and user-friendly Builds UI screen within the Quay UI.
           - Enable users to initiate and manage container image builds directly from the UI.
      • Usage Logs Integration:
        • Implement Usage Logs to provide users with insights into access patterns.
        •  Design a user-friendly dashboard for viewing usage data.
      • Authentication Login Page
        • Create a UX flow of OIDC linking quay account to an OIDC provider account like Github or RH SSO etc. upon login
      • Super User Functionality:
        • Create Super User functionality (sunsetting the panel) for administrators and privileged users where they can access advanced configurations
      • Notifications Enhancement:
        • Enhance the Notifications system to provide users with timely and relevant updates.
        • Improve the management and customization of notification preferences.
        • Ensure notifications are informative and actionable for users
      • OAuth Apps Integration:
      • Repository mirroring
        • Create the UI support for displaying, managing and triggering repository mirrors
      • Pull-Thru caching
        • Amend the organization creation wizard and UI to support the creation and management of pull-thru caches
      • Quota management and display
        • Display Storage consumption information at the organization and repository level landing page
        • Display Storage consumption information at the organization list and repository list views
        • Add Quota management / settings panel to organization

      Acceptance Criteria:

      • The new Quay UI meets parity goals and is set as the default option for all users and performs reliably.
      • Users can initiate and manage container image builds within the UI.
      • The Usage Logs feature offers accurate and updates insights into access activity
      • Notifications are improved, customizable, and deliver timely updates to users.
      • OAuth integration enabling more control of integration with other apps.
      • The Super User Panel provides advanced configurations for administrators.
      • The Quay Explore Page allows users to discover and explore public repositories with user-friendly search and filtering capabilities.

      By implementing these enhancements, we aim to provide Quay users with an enhanced and more powerful user experience while maintaining a high standard of performance, functionality and security.

       

            obulatov@redhat.com Oleg Bulatov
            qberry@redhat.com Quiana Berry (Inactive)
            Eric Rich Eric Rich
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: