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

Phase 2: MVP - Quay.io UI Launch

    XMLWordPrintable

Details

    • UI Quay.io MVP - Part II
    • False
    • None
    • False
    • Not Selected
    • To Do
    • 100
    • 100% 100%
    • 0

    Description

       

      Why is this important?

      At our face-to-face, Engineering determined the "definition of done" for the new Quay MVP UI as the following before deploying the UI publicly on Quay.io.

      Additionally other ** requirements integral to our launch in the UI is API configuration to enable scalability and implementing a UX Analytic tool to track user activity before and after our launch.

      These requirements ensure baseline parity with the current Quay.io UI that will enable user to have the most essential functionality required before demoing the beta version of the product.

      Known Constraints

      The first launch on quay.io will be without sign up page flow and will require users old login information

      UI Requirements for Launch :

      • Settings
        • User
        • Org
        • Repo
        • Authentication
        • Robot tokens
        • OAuth
        • Teams and Membership
        • Default Permissions
      • Routing
      • Footer

       

       

       

      Attachments

        Issue Links

          is related 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-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
          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-5207 Phase 3: Quay.io Summit Deliverables

          • Critical - To be worked on immediately following BLOCKER issues.
          • 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-4117 Phase 6: Net New

          • Undefined - Priority not specified.
          • Closed

          Activity

            People

              doconnor@redhat.com Dave O'Connor
              qberry@redhat.com Quiana Berry (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: