Loading Profile...
Access control
How can we restrict access to engineers and product managers, so that either can work on stories, but not adjust priorities or order of work?
I’m happy
1
person has this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
The company marked this question as answered.
-
Inappropriate?Currently there are only three levels of authorization: viewer, member, and owner. None of them restrict priority ordering while still allowing work on stories.
Viewers can only see the project, they can't change priorities, make comments, or work on stories. Members and Owners can freely edit everything about a story, including the priority ordering. In addition, Owners can alter the project-wide settings (iteration length, name, etc.)
We find that an active and engaged product/project manager mitigates most of the risk of engineers re-ordering stories. Iteration planning meetings also help. If everyone knows why a story was prioritized or de-prioritized, they are less likely to make changes on their own initiative that are in conflict with the group's goals. -
Inappropriate?Thanks for your reply. I still think it would be good to have 1-2 more levels of access control not only to restrict actions, but also to avoid accidental moves or usage of stories in ways not intended. Especially with larger and/or distributed teams.
EMPLOYEE
