Use paths from Rails in admin group and project dashboards

What does this MR do and why?

Related to #560248 (closed) and #561976 (closed)

We were hardcoding paths on the frontend for admin groups/projects lists. This can lead to URL bugs. It is better to use Rails as the SSOT for generating URLs and pass them to the frontend. In !211307 (merged) and !212658 (merged) we passed exposed the required paths to the frontend. This MR uses those paths on the frontend.

References

Screenshots or screen recordings

Groups

Before After
Screenshot_2025-12-03_at_11.24.51_AM Screenshot_2025-12-03_at_11.20.45_AM
Screenshot_2025-12-03_at_11.25.05_AM Screenshot_2025-12-03_at_11.20.57_AM
Screen_Recording_2025-12-03_at_11.26.06_AM Screen_Recording_2025-12-03_at_11.22.02_AM

Projects

Before After
Screenshot_2025-12-03_at_11.25.24_AM Screenshot_2025-12-03_at_11.21.11_AM
Screenshot_2025-12-03_at_11.25.39_AM Screenshot_2025-12-03_at_11.21.22_AM
Screen_Recording_2025-12-03_at_11.25.48_AM Screen_Recording_2025-12-03_at_11.21.42_AM

How to set up and validate locally

  1. Sign in as an admin
  2. Go to /admin/groups
    • Click on a group
    • Click the Edit action
    • Use the tabs
  3. Go to /admin/projects
    • Click on a project
    • Click the Edit action
    • Use the tabs

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

Loading