Comment 2 for bug 530180

Having written tests to demonstrate the problem, I actually wasn't able to, so I checked the permissions:

17:50 < noodles> bigjools: can you run the following on staging for me to confirm whether it gives the same results as dogfood? https://pastebin.canonical.com/28854/
17:51 < bigjools> partner | partner | canonical-partner-dev
17:51 < bigjools> primary | partner | ubuntu-archive
17:51 < noodles> Thanks. So there's the problem.
17:52 < bigjools> ha

So the permission for ubuntu-archive with partner-component needs to be on the partner archive, not the primary archive. That should fix Dustin's problem.

I'll still land my branch as it has some extra tests, and will also ensure that a user can just administer, for example, the partner archive queue (currently the logic as shown in bigjools' snippet above) assumes that the person already has queue admin rights on the main archive (which Dustin has) before checking the specific items.