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

[OCM] Explore Designs: Improve the Edit Subscription Workflow (Long term)

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Undefined Undefined
    • OCM
    • None
    • False
    • False

      Goal

      • Subscription settings are not conducive to users making a connection between their evaluation expiring and the action of subscribing on the clusters list.
      • Our goal is to encourage and enable users to make informed subscription decisions. 
      • Investigate:
        • what information we can provide to create context around how many active subs users have available per type
        • can we provide insight if subscribing this cluster will land you under or over your threshold
        • do you need to buy more to accommodate this cluster?

      Background

      • There are 1981 unclassified clusters. Having clusters in an unclassified state means that Red Hat does not understand what Custom Global Customer Name (GCN) the cluster is associated with. This limits Red Hat’s ability to engage with the owner of the cluster in a meaningful way which decreases chances of revenue generation, retention, and customer success.
      • There are several scenarios by which these unclassified clusters can occur.
      • This story's focus it to encourage customers with existing subscriptions to convert their eval to a supported one.
      • Shiri did a lot of work in this area pre Summit 2021 so worth connecting with her as well
      • There is a short term story to enhance the modal today without any API changes

      Requirements

      • Leverage the eval status both on the clusters list and the cluster details
      • If the cluster is connected to an account and has an active subscription we will default to the Subscribe option. (Configuring subscription settings requires an active OpenShift subscription)
      • For the edit subscription modal:
        • Provide the necessary cluster information so users know what cluster they are subscribing
        • Investigate what information we can provide to create context around how many active subs do they have available per type? Can we provide insight if subscribing this cluster will land you under or over your threshold? Do you need to buy more to accommodate this cluster?
        • Identify any other gaps we could be missing.

      Resources

      Other Documents to take note of
      RH Severity levels
      Product support
      RH Store FAQ
      Partner support FAQ
      Miro Board(subscription flow)
      Marvel designs

              khatchou Kevin Hatchoua
              mehall-1 Megan Hall
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: