Improve DAG name and empty state
Release notes
Problem to solve
When embarking on the DAG feature for the very first time, users feel lost due to the lack of accessible cues to start using it.
- DAG name is unclear, many users are not familiar with it.
- There's not enough guidance in the UI about what the DAG viz. feature is and how to start using it, and why.
Intended users
User experience goal
I want to easily discover the new feature in the UI, learn about it, and start using it.
Proposal
Change the name of the DAG tab to Needs, and adjust the empty state content.
- The DAG inline link should lead to the documentation for DAG
- The CTA button should lead to the documentation about the :needs keyword.
Further details
Permissions and Security
Documentation
Availability & Testing
What does success look like, and how can we measure that?
What is the type of buyer?
Is this a cross-stage feature?
Links / references
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.