If you use "browse assets" on a group repository you can find the files in the group. But there is no way to know what repository these files actually live in.
This is a critical diagnostic tool needed by support. As an example, a customer here had bad metadata files in their group repository which was causing merges to fail.
There was no way to find out what repository actually had the bad files. Note that "?describe" diagnostics are not user friendly and would not work in this case since it would end up running a merge, which would fail.
- The asset details screen should show what proxy or hosted group member containing repository the asset resides in