Forum Discussion
Limiting access to reorder Azure DevOps backlog
Hoping someone might respond here as there seem to be a lot of these type of questions that have been asked with no resolutions...
We have created a single stack rank ordered backlog and want to limit the ability for individuals to re-order these Epics. Individual work items currently live on various team boards with the stack rank order being created on a backlog which aggregates all of these team boards. I assume that order is actually dictated at the team level and then displayed on the aggregate board and if a team was to move the work item it would also move on the aggregate board...
Has anyone done this? Any ideas on how to limit who can change the stack rank order?
You may organize your backlog using a hierarchy of work items as first step:
Epics: Higher-level containers that group related features or scenarios
Features: Intermediate level that rolls up into epics. Features often represent major deliverables
Backlog Items (User Stories, Tasks, Bugs): Smaller deliverables that roll up into featuresKidd_Ip thanks for your response.
Currently we do have work items organized in this way with open permission levels for anyone in the organization to create these work items. I'm curious to know how this organization supports doing what I am looking to do - I'd love more details on why you made this recommendation other than it is standard structure?
