Display existing planning hierarchy at the project level
Problem
You cannot see the default hierarchies that exist in GitLab and how they related to other non-parented objects like issues, incidents, and requirements.
Release notes
Right now, the only way you can see the existing hierarchies that relate to your project is to click on one epic at the group level or view parenting structure in the sidebar of an issue. Unfortunately, this does not give you a high-level view of how your epics and issues relate and are structured.
In 14.6, we added the ability to view your existing default issue types, epics, incidents, and requirements at the project level in one simple view. Understanding how you are structured is essential to aligning your team around how you want to structure your work.
This MVC is read-only, but it sets the stage for some new changes that are coming for GitLab and will make this even more valuable: 1) moving epics onto issue types and 2) having groups and projects merge.
Proposal
- MVC Expose them in the UI at the Namespace (Project/Group) level.
Current:
- Epic
- Issue
Stand alone:
-
Requirement
-
Test Case
Next steps (future):
- Allow adding new work item types
- Allow parenting and nesting of items
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.
MVC Solution
- Add a
Hierarchy
navigational item to Project settings- Add a banner soliciting feedback on work items. Survey to be completed here: ux-research#1695 (closed)
- Add a
Current structure
andUnavailable structure
section to this newHierarchy
page- Add a very MVC section displaying the user's current hierarchy
- Add a very MVC section displaying the hierarchy unavailable to user's due to tier
- Add tier badge next to unavailable items indicating what tier is required
- Add
tip
banners to list views like requirements, epics, and issues to indicate that there is a hierarchy view page. -
🎨 Figma: https://www.figma.com/file/9lz6cyeISThJnXsqMSQ0ns/340844---Display-default-(existing)-hierarchy-in-Project-Settings?node-id=17%3A12095