Utilize breadcrumbs to reenforce user understanding of organizational objects (Groups, subgroups, projects, and beyond)
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Problem to solve
It isn't inherently obvious if the user is in a group, subgroup, or project just by viewing the breadcrumbs. We are also assuming a user understands that they are in an Epic, MR, or Issue just by viewing the symbol proceeding the number, or perhaps the prior breadcrumb.
| Epic | Issue | Merge Request |
|---|---|---|
![]() |
![]() |
![]() |
How might we make breadcrumbs more clear and assessable holistically across GitLab?
Proposal
| Using clearer labeling | Using icons | Using both |
|---|---|---|
Anything else?
Edited by 🤖 GitLab Bot 🤖


