[VSA] Add empty state at the group level when there are no custom value streams

Description

With upcoming changes to how the VSA backend works we will no longer have a default value stream available for new VSA groups, VSA also currently does not have an "empty" state, this is because we have always had an "in memory" default value stream available.

The empty state region guidance in Pajamas recommends the Configuration required pattern as the most appropriate solution here.

Configuration required

A Configuration required empty state serves as a placeholder for features that need to be configured first, before having the ability to create content.

Specifications
  • Contains a primary action for configuring a feature.
  • Contains a secondary action for inviting a member to configure a feature. The secondary action should read as Invite member to configure, which should trigger the invite modal.

Solution

Before After
127.0.0.1_3000_groups_group-test_-_analytics_value_stream_analytics_created_after_2022-01-18_created_before_2022-02-16_value_stream_id_default image
We are unable to continue to use this as the view when we use the new backend. (Source) Annotated Figma file

Location

Group > Analytics > Value stream e.g. https://gitlab.com/groups/gitlab-com/-/analytics/value_stream_analytics

Use case

  • Blank content
  • Empty search results
  • Configuration required
  • Higher tier

Checklist

Blank content

 - [ ] The solution follows the Blank content specifications in Pajamas. - [ ] Follow the instructions from the After merge section below to add Snowplow tracking.

Empty search results

 - [ ] The solution follows the Empty search results specifications in Pajamas. - [ ] Follow the instructions from the After merge section below to add Snowplow tracking.

Configuration required

  • The solution follows the Configuration required specifications in Pajamas.
  • Ask a Growth product manager or Designer to review your solution.
  • Is your solution introducing a new empty states or modifying an existing one?
    • Introducing a new empty state: Follow the instructions from the After merge section below to add Snowplow tracking.
    • Modifying an existing empty state: Follow the Experimentation process below. Note: If the empty state you want to replace hasn't been updated in a long time, doesn't pitch the value of the feature, or does not contain a next step action CTA, then we recommend you skip the experimentation process to implement and add tracking to your new empty state.

Experimentation

 - [ ] Collaborate with a Growth product manager to help you determine if you can validate your solution through an experiment on SaaS. - [ ] If an experiment is possible, create an issue using the experiment idea template and follow the template intructions. Otherwise, follow the instructions from the After merge section below to add Snowplow tracking. - [ ] Ask a Growth product manager or Designer to review your experiment set-up. - [ ] Implement and monitor the experiment following the implementation guide. - [ ] Review and discuss the findings. - [ ] Add the findings to the Growth experimentation knowledge.

Higher tier

 - [ ] The solution follows the Higher tier specifications in Pajamas. - [ ] Ask a Product Manager or Designer from the Conversion group to review your solution. - [ ] Is your solution introducing a new empty states or modifying an existing one? - [ ] Introducing a new empty state: follow the instructions from the After merge section below to add Snowplow tracking. - [ ] Modifying an existing empty state, follow the Experimentation process below.

Experimentation

 - [ ] Collaborate with a Growth product manager to help you determine if you can validate your solution through an experiment on SaaS. - [ ] If an experiment is possible, create an issue using the experiment idea template and follow the template intructions. Otherwise, follow the instructions from the After merge section below to add Snowplow tracking. - [ ] Add a ~"Category:Conversion Experiment" label to the experiment idea issue. - [ ] Ask a Product Manager or Designer from the Conversion group to review your experiment set-up. - [ ] Implement and monitor the experiment following the implementation guide . - [ ] Review and discuss the findings. - [ ] Add the findings to the Growth experimentation knowledge.

After merge

  • Use the Snowplow event tracking issue template and open an issue to add Snowplow event tracking to your new empty state solution.
    • Add your ~devops:: and ~group:: labels to the new issue.
Edited by Dan MH