MVC Design- Epic links

MVC synthesis from &7531 (closed)

Epic linking MVC

For MVC, users should be able to:

• Understand the use case of epic linking and the purpose of the widget.
• Understand if they have permission to link epics.
• Link epics across groups to the current epic.
• Understand the group assignment of epics.

MVC flow

🎨 Improve the empty state of the linked issues and epic widgets. #359145 (closed)

• Remove the info icon and link, and add copy to the body of the widget with context on use case. Add a learn more link within this copy that links out to the docs page that the info icon previously linked to.

🎨 Allow users to add epics across groups #359146

• Add a Group dropdown to better indicate to users from which group they are adding and searching from

🎨 Small UI updates

• Change the add icon button to a default button that reads Add. Align this to the right, similar to other widgets.
• Space the issue/epic count 1rem from the title

Improve epic tree usability and consistency

The epic tree styling differs from other similar widgets within work items like issues and MRs. The usability of switching views within the epic tree should be improved to allow for better labeling and consistency. The epic tree should also be easily differentiated from similar objects like Linked epics

🎨 UI updates #352329 (closed)

• Move the epic & issues and roadmap tabs/seg buttons within the body of the widget
• Move the Show labels option to the body of the widget as well, aligned right in the same row as the view options
• Add a title to the widget. Currently thinking here is Child epics and issues
• Contain the roadmap view within the widget itself