Surface project details on confirmation screens for destructive actions

Release notes

To avoid accidental destructive actions being confirmed by users, it can be helpful to surface some detail of the impact of the action. This will give an extra notice for users when reviewing their action, before confirming.

Problem to solve

GitLab's user interface should help users to avoid potential mistakes when repeatedly performing project maintenance tasks, such as Archiving, Transferring and Deleting projects. There are explicit warnings that these actions can have unintended side effects or are irreversable, but apart from mentioning the project name, there is nothing to call out what the impact will be.

Proposal

For a project especially, if the user is asking it to be transferred, the path changed, or the project be deleted, then some more cueues should be offered on the confirmation screen:

list the number of open issues/MRs
list the number of project members and stars
highlight the current visibility (public or private) and the group it is currently in

Having these listed is more context which the user can evaluate to see the impact of their change, rather than just a project name which might be very similar to the project they intend to change.

Intended users

Project Owners who are performing maintenance or administrative tasks.

Personas are described at https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/

Feature Usage Metrics

Reduction in requests for project restoration on gitlab.com
Reduction in Support requests for assistance in accidental private project exposure