TFS 2018：查看实例级别的信息

Question

We are using TFS, in this case, for our project management (Work section).

I have a server (TFS) with a collection (Default Collection) and a project (My Project)

I have created a TFS group under that project (Consultants)

Consultant permissions are then set as appropriate for their role- including " view project-level information ".

When going to the Work part of "My Project" it says the user needs " view instance-level information " which isn't an option at the project level, only for a group made at the Collection Level.

It seems impractical to create "Consultants" groups at the Collection level- as each of my projects will have a "Consultants" group with different membership and I would need to create the groups as "My Project Consultants", "My Other Project Consultants", Etc. It also seems intuitive to create the groups at the project level as they are a project scope group.

It seems counter to logic that Collection-level groups are required to give Project-level rights.

So, My question is, do I really need to create my groups at the Collection level and give them " view instance-level information " or is there a way to assign the Project-level group appropriately without creating it as an Instance-level group?

Answer 1

There is also a sever level View instance-level information permission.

First, please double check if you are lacking sever level or collection level View instance-level information permission.

The permission in TFS could be inherited, you should make sure project\\Consultants in the sever level group or collection level group which has View instance-level information permission.

The project group Consultants could also inherite the corresponding permission. For example, Project Collection Valid Users which contains all users and groups that have been added anywhere within the collection. You should check if this group lacking of corresponding permission.

Moreover, you should also check the access level for the users in project\\Consultants group. People with Stakeholder access level also have limitation features through the web portal.

Answer 2

[collection]\\Project Collection Valid Users did not have the View instance-level information set to Allow . (I thought it was by default?) Once I changed that, it resolved the issue.