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

Quay UI enhancements

    XMLWordPrintable

Details

    • Epic
    • Resolution: Unresolved
    • Major
    • None
    • None
    • quay
    • None
    • Quay UI enhancements
    • To Do
    • 42
    • 42% 42%
    • 0

    Description

      Goal: Enhance the performance and effectiveness of the Quay UI.

      Why is this important: Repository owners and first-time users of Quay or a particular repository will use the UI to configure and explore contents. Repository owners expects efficiency gains by using the UI as opposed to the APIs, for example for batch / group operators. Users require a responsive interface while not putting the Quay services under massive load.

      Prioritized deliverables

      • responsive frontends that are easy on the API server side
      • batch operations for most common tasks
      • regex patterns in search fields
      • organizations as top level navigational concept

      Optional deliverables

      • less clicks to get a pull command
      • navigation shortcuts to sub menus in list views
      • status icons of repos with build status, notifications, private / public status

      Attachments

        Issue Links

          relates to

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. PROJQUAY-5434 Part II: New UX Journey to Console.rh

          • Critical - To be worked on immediately following BLOCKER issues.
          • New

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. PROJQUAY-5456 Phase 4: Core UI Functionality

          • Critical - To be worked on immediately following BLOCKER issues.
          • New

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. PROJQUAY-3203 Part I: Migrate Quay.io web presence to HAC

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. PROJQUAY-3865 Phase 1: MVP UI for Normal & Superusers

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Activity

            People

              Unassigned Unassigned
              DanielMesser Daniel Messer
              Votes:
              1 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

                Created:
                Updated: