"Deploy keys from projects you have access to" may be incomplete when logged in as admin
Summary
When adding the same deploy key to more than one project, one must pick the existing deploy key from the list "Deploy keys from projects you have access to" and enable it for the other project rather than adding it again.
However, when you are logged in as admin user, despite having implicit access to all projects, this list includes only projects where you are actually a member of (either directly, or indirectly through group membership).
Steps to reproduce
- Log in as admin user.
- Add SSH deploy key to project A where you are not a member.
- Go to project B and look for SSH deploy key in list "Deploy keys from projects you have access to".
What is the current bug behavior?
The SSH deploy key from project A is not listed in "Deploy keys from projects you have access to" despite the admin user having access to project A (otherwise, they would not have been able to add the deploy key there in the first place).
What is the expected correct behavior?
The list "Deploy keys from projects you have access to" should include keys from all projects when one is logged in as admin user.
Possible fixes
Arguably, this issue might be considered a feature request rather than a bug report—perhaps the current behavior is intended. In the very least, I would suggest documenting the fact that the list "Deploy keys from projects you have access to" contains keys of projects "you are a member of" rather than "you have access to", so maybe a simple rewording is sufficient here.
Ideally, however, an admin user should not be required to be a member of every project they want to manage SSH deploy keys of—being a member is not required to add one deploy key to the first project, so it should not be required to add the same deploy key to another project.