Uploaded image for project: 'OpenShift UX Product Design'
  1. OpenShift UX Product Design
  2. PD-942

Identify gaps that prevent a shared masthead

    XMLWordPrintable

Details

    • Story
    • Resolution: Done
    • Major
    • Admin
    • None
    • OpenShift UXD Sprint 202, Console UXD Sprint 203

    Description

      In the short-term the items within the masthead when “All Clusters” is selected will be slightly different than when a single cluster is selected - e.g. the Notifications drawer is no longer available because it’s single-cluster scoped. We should investigate what gaps exist and create additional stories (if needed) for any differences that require additional design work to reconcile.

      Example: the link to ACM’s Visual Web Terminal could likely be available at all times regardless of whether “All Clusters” or a single cluster is selected. The Notification drawer disappearing might require us to dig deeper into multi-cluster monitoring, but in the short-term we should decide whether the icon disappearing is okay or if a quick tweak could improve the experience until then.

      Design

      Attachments

        Issue Links

          is related to

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. PD-947 Explore: "All Clusters" Hybrid Console User Preferences

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • To Do

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. PD-1018 Investigate Combined OpenShift Console logo and About modal

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • To Do

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. PD-935 “All Clusters” Getting Started experience and Quick Starts

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • To Do

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. PD-1016 Single/Multi-cluster search integration

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed
          relates to

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CONSOLE-2838 Align masthead with ACM

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

          Activity

            People

              bmignano Brie Mignano (Inactive)
              abrarenrh Andy Braren
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: