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 ...
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 features
Kidd_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?
