Skip to content

Refactor and adjust styling on group/project list actions

Peter Hegmanrequested to merge
556523-groups-projects-list-view-update-actions-dropdown-styling into master

What does this MR do and why?

Related to #556523

Refactors the list actions component that is used on group and project lists. Previously the order of actions was determined by the availableActions prop. This opened up possibilities of inconsistencies between lists. It also made it so we couldn't separate the danger actions from regular actions.

References

Screenshots or screen recordings

Groups

Before After
Screenshot_2025-10-20_at_10.45.13_AM Screenshot_2025-10-20_at_10.25.50_AM

Pending deletion group

Before After
Screenshot_2025-10-20_at_10.45.40_AM Screenshot_2025-10-20_at_10.26.18_AM

Archived group

Before After
Screenshot_2025-10-20_at_10.46.09_AM Screenshot_2025-10-20_at_10.26.43_AM

Projects

Before After
Screenshot_2025-10-20_at_10.43.21_AM Screenshot_2025-10-20_at_10.21.44_AM

Pending deletion project

Before After
Screenshot_2025-10-20_at_10.43.50_AM Screenshot_2025-10-20_at_10.22.10_AM

Archived project

Before After
Screenshot_2025-10-20_at_10.44.20_AM Screenshot_2025-10-20_at_10.22.38_AM

How to set up and validate locally

  1. Go to /rails/features and enable archive_group feature flag
  2. Go to /dashboard/groups
  3. Use actions
  4. Go to /dashboard/projects
  5. Use actions

MR acceptance checklist

Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Edited by Peter Hegman

Merge request reports