CODEWITHSUNDEEP
permissionsazure-devops
M0053
M0053

Reputation: 13

VSTS Restrict access to sensitive work items

Foreword: I've searched around on this question a fair bit and found answers which are close to a solution, but not what I'm looking for. So here I am, and I hope someone can help me. I'm relatively new to VSTS, so be gentle (or at least constructive) ;P

The Question: I'm looking for a way to restrict access to specific tickets (NOT by ticket type) that contain NDA protected data, whilst keeping them in the same backlog and iterations as the rest of the tickets related to a project.

We have many different NDA protected customers, so whilst creating a new ticket type per NDA, and restricting access to this, could work, it's not the solution I'm looking for. Alternatively, I'm barking up the wrong tree, and there is an entirely different and "better way" to support this use-case?

Edit 1 - More info: Let's say I have 1 backlog for a product. It contains only 2 work items. It's important there is only 1 backlog for planning and overview by a product owner.

One of the two work items contains sensitive information only half the development team should have visibility to. How do I keep both tickets in the same backlog and iterations, but hide the sensitive one from some team members?

Thanks in advance for your time!

Upvotes: 1

Views: 354

Answers (1)

starian chen-MSFT
starian chen-MSFT

Reputation: 33708

Regarding permission of work items in a team project, you can set the permission in area and iteration scope, but can’t for specific work items.

So, you need to put these work items in different area and manage permission for this area. Simple steps:

  1. Go to team project admin page
  2. Work=>Areas
  3. Click New/New child, to create a new area.
  4. Click …=>Security, set the permission for the group(s) or user(s)
  5. Click the default team’s settings => Areas
  6. Click + Select areas to add that area in order to show related work items (in that area)

Upvotes: 1

Related Questions