Allow users to assign themself or a teammate to an epic from an epic itself
Problem to solve
This is similar to the epic boards larger job of:
Parker: When facilitating planning at scale across many teams or groups within my organization, I want a high level view of how my epics are moving through a workflow, so that I can track and report on the progress of features and initiatives.
Assigning epics to teammates or oneself allows our users have better context of who is responsible for these larger work items or actively working toward progressing them.
As a user planning work prior to any issues or MRs existing,
I need to be able to find and manage epics I am responsible for,
So I can easily move an epic through my workflow
Parker:
Intended users
Proposal
MVC will be very similar to the current assignee experience in current MR and issue sidebars. As we improve this experience, we will improve consistently across all of these areas.
For MVC:
-
Add the
Assigneeoption underTo Doand above the date selection -
Users can quickly assign themselves without clicking
Edit -
Users can assignee no one, one user, or many users
-
Figma link: https://www.figma.com/file/RYyyYL8Vmr8I4qvpfnAiSO/Epic-assignees?node-id=54%3A1592
| Sidebar expanded | Sidebar collapsed | Current assignee experience |
|---|---|---|
![]() |
![]() |
![]() |
Further details
As we move to launch Epic/Program Boards &2864 we will be enabling users to work epics through a workflow just like issues. Assignment is a key part of common workflows involving epics, especially prior to individual issues being created and assigned.
Product, Eng Managers, and Program Managers will need to assignee themselves to epics they are responsible for, and easily access them.
Permissions and Security
Same as epics in GitLab Premium and GitLab Ultimate
Documentation
- Need to update epic documentation
What does success look like, and how can we measure that?
- We can track number of users who have an epic assigned to them to follow adoption
What is the type of buyer?
Per our buyer model :
- Premium is for multiple team usage, with the purchasing decision led by one or more Directors
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.


