<!-- This template is a great use for issues that are feature::additions or technical tasks for larger issues.--> ### Proposal Currently, when checking at Geo site components under _Admin > Geo > secondarysite_ you will see an internal reference number which often would not make sense to customers as exploration will need to be done on the Rails console to match the specific object to a given project, artifact_id, Wiki, etc. By displaying the same reference of what a customer sees from GUI it will be easier to pinpoint which components is not synchronized or needs attention. The following example shows of artifacts id and projects id that from the geo repository registry. This is not intuitive. If it could show the actual project number or even better a link to the affected project ID it would be awesome!   See https://gitlab.com/gitlab-org/gitlab/-/issues/536297#note_2966720679 for a more detailed description of requirements. <!-- Use this section to explain the feature and how it will work. It can be helpful to add technical details, design proposals, and links to related epics or issues. --> <!-- Consider adding related issues and epics to this issue. You can also reference the Feature Proposal Template (https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Feature%20proposal%20-%20detailed.md) for additional details to consider adding to this issue. Additionally, as a data oriented organization, when your feature exits planning breakdown, consider adding the `What does success look like, and how can we measure that?` section. --> <!-- Label reminders Use the following resources to find the appropriate labels: - Use only one tier label choosing the lowest tier this is intended for - https://gitlab.com/gitlab-org/gitlab/-/labels - https://about.gitlab.com/handbook/product/categories/features/ -->