Work item types in Azure Boards depend on the process template chosen at project creation -- Basic uses Epic, Issue, and Task; Agile uses Epic, Feature, User Story, Task, and Bug; Scrum uses Epic, Feature, Product Backlog Item, Task, and Bug -- and switching to a different process later requires a migration rather than a simple setting change. Work is organized across teams using area paths, which assign items to a team or component, and iteration paths, which assign items to a sprint or release; each team backlog and sprint board is a filtered view over that shared pool of work items.
- Work item types are set by the process template chosen at project creation
- Area paths and iteration paths scope work items to teams and sprints respectively
- Each team backlog and board is a filtered view over shared work items, not a separate item pool
Use cases
Intro
- Create a repository and manage branches in Azure DevOps
- Submit code changes via pull requests in Azure DevOps
- Enforce branch policies and reviews in Azure DevOps
- Integrate issue tracking with commits in Azure DevOps
- Audit and rollback changes if needed in Azure DevOps
Closing