Adding a team to a project grants only view access;
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 59.6k
- Forks
- 5.8k
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 49
Description
Hi!
When a team is added to a project, the team's members receive read-only access. They can view work items but cannot create them. To grant create permissions, each team member has to be added to the project individually as a project member. This defeats the purpose of team-based access and is confusing in the UI, since adding a team to a project gives the impression that the team's members will inherit the expected level of access.
Is this an expected behaviour or a bag?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported behavior: add a team to a project and verify whether its members can view work items but cannot create them. Compare that result with adding a member individually, then confirm that the expected behavior is for team members to inherit the team's project access needed to create work items.
Written by the indexing model from the issue text.
Assessment
- Domain
- authorization
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100