imeredith, since this one's marked as In Review, could you put in a link to the PR? Many thanks.

Testing Notes:

• This is a one-line change to a Jelly file (a deletion, actually). A one-shot visual verification would suffice.
• We should be mindful of JENKINS-45476, as well, and make sure this doesn't end us up with >1 "Open Blue Ocean" links on the left side.

elatt I thought I had found fixed this but then realised I did something totally different. I can't replicate the issue. I created a job and added the matrix auth to it, and then only gave it READ and DISCOVER, and the link was in the side bar.

Can you plase try the latest code, and also provide steps to replicate it incase im missing something. Cheers.

kshultz Do you want to delete the testing notes?

Actaully spoke too soon. While working on another ticket I just saw this based on the job I set up to test it.

This occurs when you are logged in as a user that has global permissions, but is not covered by the project based matrix permissions.

Never mind, I can't replicate it again. I'm not sure if I did replicate it, or if for some reason I just missed the link somehow.

Your note about being a global admin but viewing a project that you weren't explicitly given permissions to sounds plausible. However, I no longer have access to that Jenkins environment where I filed the issue so I don't know if I will be able to reproduce. Some more insights are, I was a global admin, the job type was a Pipeline job and it was either as you describe above with the permissions or there were also some jobs where we had "don't inherit permissions" but then a group that I was a member of was giving the normal set of read/write/build/etc permissions along with other groups being given read-only/build access to the job.

Closing this. Can't replicate it for now.