Repository creator (team admin ) does not have access to private forks by other team members

Consider a private team with an admin member. The workflow adopted is 'forking'.

a) The admin member creates a private repository and assign it to the team as owner.

b) The access page now shows <team name> as owner and <admin name> as creator.

c) Some team members are given read access to this repository.

d) These team members privately fork the repository (ensuring that permissions are inherited) and begin work.

e) The admin member sees 0 forks on the repository and cannot monitor the team's copies.

f) The admin member cannot be granted any further access as he/she already is 'creator'.

g) Workaround is that if logged in with the team username the number of forks are correctly reported and the member's repos can be watched.

h) However as team logins are soon to be deprecated this will not be possible at all.

In my opinion this is critical functionality for private teams working with a forking workflow.