<!-- This issue template can be used as a great starting point for feature requests. The section "Release notes" can be used as a summary of the feature and is also required if you want to have your release post blog MR auto generated using the release post item generator: https://about.gitlab.com/handbook/marketing/blog/release-posts/#release-post-item-generator. The remaining sections are the backbone for every feature in GitLab. The goal of this template is brevity for quick/smaller iterations. For a more thorough list of considerations for larger features or feature sets, you can leverage the detailed [feature proposal](https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Feature%20proposal%20-%20detailed.md). --> ### Release notes <!-- What is the problem and solution you're proposing? This content sets the overall vision for the feature and serves as the release notes that will populate in various places, including the [release post blog](https://about.gitlab.com/releases/categories/releases/) and [Gitlab project releases](https://gitlab.com/gitlab-org/gitlab/-/releases). " --> ### Problem to solve <!-- What is the user problem you are trying to solve with this issue? --> For Product Analytics, we need to introduce several new screens for the user to interact with. This includes approximately five screens for dashboards, query building & configuration, and cluster configuration settings, and funnel analysis, at a minimum. These screens need to reachable via the left sidebar while also complying with our design and product guidelines. ### Proposal <!-- Use this section to explain the feature and how it will work. It can be helpful to add technical details, design proposals, and links to related epics or issues. --> There is a short-term plan as well as a directional vision for how we will add these screens. This is intended to mesh with the existing menu system and offering in the product. Add new options under the existing `Analytics` tab. Specifically: * Add a new `Dashboards` item * This is where all the Product Analytics dashboards (e.g. `Audience` and `Behavior` will live. * Over time, the existing dashboards (e.g. `Value Stream`,`CI/CD`, etc) on the `Analytics` tab will move here as individual dashboards that can be viewed. * Once `Value Stream` is moved over, we can direct the `Analytics` main item to link to `Dashboards` rather than `Value Stream`. * Add a new `Configuration` item * This is where Product Analytics configuration (Jitsu/ClickHouse/Cube.dev) will go * Any additional configuration screens needed for new dashboards or features will go here * Add a new `Funnel` item * Once built, this is where Product Analytics funnel features will live * Add a new `Experiments` item * Once built, this is where Product Analytics experimentation capabilities will live Short term this will look like:  Longer term this will look like:  The longer-term vision may change as we iterate and learn more. <details><summary>Previous work</summary> There are several approaches we have discussed up to this point for where to introduce these new screens: 1. Introduce a single screen called `Product` under `Analytics` to house one screen and link from that screen to others * This has the downside of needing to add links from a top-level page to subpages, which isn't an ideal UX. * We don't have the concept of sub-submenus to be able to fan out multiple links from the `Analytics->Product` option. 1. Introduce a new option, `Product Analytics`, to the left sidebar * This would be confusing for users to see both `Analytics` and `Product Analytics` on the left sidebar. * It would give us flexibility to add as many new screens as we needed. 1. Utilize the existing `Analytics` tab for all Product Analytics screens and move the existing options to new locations. * This would be ideal from a Product Analytics perspective but would require thoughtfully relocating the existing 7 screens. * <details><summary>Proposed Update</summary> Value stream -> Value Stream Management / Optimize <br/> CI/CD -> CI/CD (therefore renamed to something like CI/CD -> Analytics (or Charts, its current URL slug)<br/> Code review -> Security & Compliance<br/> Insights -> Value Stream Management / Optimize<br/> Issue -> Issues (renamed as something else as a sub-item)<br/> Merge-Request -> Merge Requests (renamed as something else as a sub-item)<br/> Repository -> Repository (renamed as something else as a sub-item)<br/> </details> 1. Re-name the existing `Analytics` tab to `Product Analytics`, move some of the existing items under `Analytics` to new sections, and introduce new left sidebar options for other analytics-related items (such as Value Stream Analytics) * This is again ideal for Product Analytics, but would require thoughtful planning. * Adding other Analytics use cases, such as Value Stream Analytics, to the left sidebar could make it become cluttered. 1. Enable the concept of sub-submenus to be possible within Pajamas * UX team has intentionally not done this previously, so would be controversial. 1. Add `Dashboard`, `Settings`, and other Product Analytics screen links to the existing `Analytics` sidebar option and leave the existing other options there. 1. _fill in other ideas_ ### Open questions 1. Can we feature flag where these will live on a per-project basis? * If so, perhaps we could update the screens to only appear on the internal handbook project page, and then we can iterate from there before a full rollout to all of GitLab. This would also let us expose it on an as-needed basis if we pursue a closed beta. <!-- Label reminders Use the following resources to find the appropriate labels: - https://gitlab.com/gitlab-org/gitlab/-/labels - https://about.gitlab.com/handbook/product/categories/features/ --> </details> <!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION --> *This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.* <!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION -->