Migrate link button to tertiary in epic roadmaps
What does this MR do and why?
As part of &4232, we updated our styling of the link variant button to represent a link (blue text). With this change, we also introduced a new button category (tertiary), which are styled as secondary buttons without a background or border. Prior to this change, the link variant was often used in cases where a button was needed without a border.
Epic roadmaps were previously using the link variant and can use the tertiary variant instead.
Related to #241589 (closed)
Describe in detail what your merge request does and why.
Screenshots or screen recordings
| Before | After - resting | After - hover | After - expanded |
|---|---|---|---|
 |
 |
 |
 |
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
How to set up and validate locally
- Visit a group
- Go to Roadmaps (you need epics to populate this - follow https://docs.gitlab.com/ee/user/group/roadmap/). Epics need to have dates assigned to them for them to show up in roadmaps. Add child epics to epics for many nested levels.
- Expand/Collapse the epics within the milestones sidebar.
Numbered steps to set up and validate the change are strongly suggested.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.