I have a public Azure DevOps project, and I want to allow everyone to add Work Items.

However, adding the Readers group as a member of Contributors for the permissions doesn't change anything, and I can't find "Add Work Items" but only the "Delete Work Items" toggle for changing its own Readers perms so I am really stuck here.

The contributors perms: enter image description here

Having to add every mail account to allow people to add work items isn't possible in my situation (Game Engine project) so I really have to find a solution.

  • Even Stakeholder access level has permission to add work items now. What exactly does a user experience when trying?
    – Crowcoder
    May 1 '20 at 22:21
  • I have tried that, but unfortunately you can't inherit the group Readers to the group Stakeholder so everyone is able to work items, for a reason I ignore. So they just don't have any perms other than what allows Readers.
    – iyenal
    May 2 '20 at 23:02

Usually each projects would have teams defined with the team members. So if you have a team defined then add the team to the contributors list.

  • Unfortunately I did already, but it doesn't change anything :(
    – iyenal
    May 17 '20 at 12:20
  • See if the same members\team are added as Readers. Azure DevOps might be using inherited permission. Try removing the contributors from readers list.
    – Jerry
    May 18 '20 at 8:37

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.