The new section in the sidebar should only appear if the epic's group is in EEU (for GitLab.com), or the self-hosted instance has a EEU license.
Also for subgroups of a EEU group would work the same since subgroups of a EEU group have EEU functionality. That is, that new section would appear in the case that epic is in that subgroup.
Out of scope
In the future, we may consider assigning an issue to an epic from the issue itself. That is not in scope here. So therefore, it's just a link.
Edge cases
None so far
Designs
Expanded (filled)
Expanded (empty)
Collapsed
It should use the epics icon from the navigation sidebar.
If there's no associated epic, the area should just say None.
The tooltip contents to show the full epic title
If there's no assigned epic, we just show “Epic” in the tooltip.
@pedroms : See the attached mockup. Feel free to change it and provide other designs.
@smcgivern@jarka : I think that for a given issue's project, the ancestor groups can only be less restrictive right? So I don't think there's a scenario where if you have access to an issue, that you should not be able to see the epic? So we don't have to worry about that case to account for not showing the epic link/name because of permissions?
@pedroms : We also need a design for collapsed sidebar.
@ClemMakesApps : Yep should be. Updating the description to be explicit. I'll let @pedroms make any changes he wants. I think a future issue is doing the inline tier upsell UI we've had for some other features. But let's definitely not worry about that now.
@ClemMakesApps could you please specify what exactly you need here from backend? There is a request on issue detail page for sidebar data (eg. https://gitlab.com/gitlab-org/gitlab-ee/issues/3696.json?serializer=sidebar) and I suppose you just need to include epic here (id, title, maybe link?)
@jarka : What do you mean you haven't implemented EEU check on group level yet? How is it working already by not showing epics when you are not in EEU?
could you please specify what exactly you need here from backend? There is a request on issue detail page for sidebar data (eg. https://gitlab.com/gitlab-org/gitlab-ee/issues/3696.json?serializer=sidebar) and I suppose you just need to include epic here (id, title, maybe link?)
ID, title and link sounds pretty reasonable to me. @pedroms can you confirm that the mockup in the description is the final UX? I'm hoping to get started on this tomorrow
@victorwu why is the metadata title is “Parent” instead of “Epic”? “Parent” may lead users into thinking of parent/child issues and how that metadata has anything to do with “Related issues”.
@pedroms : Can you please update the description for the SSOT. I think when blank, there should be no tooling? Please update with the correct mockups. Thanks!