Team Administrator don't have access to private repositories (BB-4888)
I just created a new team (well, converted to a team) and gave one of my members explicit 'admin' access to all repositories.
According to logic, the added member should have read/write access to all team repositories regardless of their public/private status. They are, after all, 'administrator' members.
However this is not the case. The member I explicitly gave admin rights to could see all private repositories but could not even read from them. Yet he could go in and change the public/private status at will, as well as perform all other administrative functions.
This is really bad design, and should be fixed. At the very least, team administrators should have a minimum of read access to private repositories but that somewhat defeats the purpose of the 'administrator' type.