Hide Area and Iteration Names users don't have permission to view
In TFS 2010 we can set permissions on areas and iterations to limit access to work items and queries. However, all TFS users can still see the names of all area and iteration nodes regardless of permissions. There should be permissions that limit the visiblity of area and iteration node names.
Scenario: We use a single team project for development of multiple products for multiple different customers. We configure areas and iterations for each different customer/product and set permissions on those nodes to limit access. Some customers and products are highly confidential and the associated area and iteration names should not be visible TFS users unless they have been granted access.
We’re not planning to do this. We do plan to update both the area and iteration selection dialogs to be more usable… but no plans to restrict values there based on permissions.
Feel free to reach out if you can’t live without this one.
Ed Boykin commented
Add my vote to be able to hide older iterations. My iteration list is getting loooong.
Jon Hardcastle commented
I'd like this too.
i also look forward to this feature.
I want to be able to Hide old Iterations SO, that user don't have to scroll it to a big list to get to the iteration they want to choose.
I am working in BFSI org with employee> 20000 wordwide. I am also looking for similar feature where even View Rights may be denied on Workitems .
I am not sure what this "view node" permission even does... versus what I wish it would do. As a customer, my having to experiment with all variations in the tool to see how it works - and then having to work with others under their various credentials to see the results of these permission variants - gets more than annoying... I realize there is "documentation" in the MSDN site... but it brings none of this operational information to light. The customer-friendly thing to do... be more thorough in your documentation so you are not wasting our time. [IMHO] If you don't have time to code it - you could at least properly document it. I have hundreds of projects, hundreds of users, and a real need to manage visibility and security... consider how poorly the tool facilitates this.