Epic to Issue relationship enhancements
Problem to solve
It is cumbersome to tie each issue to an epic AND to a milestone.
Target audience
-
Parker, Product Manager, https://design.gitlab.com/research/personas#persona-parker
-
Delaney, Development Team Lead, https://design.gitlab.com/research/personas#persona-delaney
Further details
Associating issues with epics directly through a link seems like it would be problematic. It seems like some issues will slip through the cracks - not getting assigned to epics. Instead why not let that association happen automatically through milestones. I.e. Epic has 1 or more group milestones, group milestones have one or more project milestones and project milestones have many issues...
Proposal
It would be easier if you could instead connect group milestones to epics and then assign all issues in a milestone to that epic (automagically). You could go further and assign the project milestones to a group milestone and track both group and project milestones from the same epic without having the issue > epic > milestones disconnect.
Furthermore, linking issues(or milestones) by their link is confusing. Why not have a nice search?
What does success look like, and how can we measure that?
Epic to Issue association should happen automatically as part of the natural workflow. I.e. via milestone assignments or perhaps labels. As an ADD type personality I don't want to have to sort through issues or copy/paste links between the issues and epics pages.. yuck