- The Organization is the Root of the Azure DevOps (ADO)
- Projects are the highest level Azure Devops Container -- Everything lives within a project
- Teams are groups of people -- managed within a project
- Boards are for managing teams -- Select on login or at the top of the page
- Boards implement a Process (Basic, Agile, Scrum, Custom)
- Processes are defined / managed at the Organization Level
- Processes are highly configurable, and define the schema for the boards and work items
- Boards use 3 central concepts: Work items, Queries, and Views
- Every thing is a work item
- Some items can contain other items as defined in the Heirarchy:
- Tasks and Bugs are "Atoms": they describe work to be done and cannot contain other work items
- Product Backlog Items (PBIs) and User Stories are Atom Containers: They contain atoms (Tasks and Bugs).
- Epics and Features contain other containers (PBI's and User Stories)
The top left of each view has a group of icons responsible for configuring the view and filtering the work items displayed in the view.
- Views are always filtered
- Boards and Backlogs are filtered by Item Type (Backlog, Feature, or Epic -- AND THAT's ALL)
- Sprints are filtered by person ane iteration
- All views have additional filter options
- Styles can be customized, but custom styles are specific to a view (e.g. tag color)
- Work Items: A flat list of all the objects (hence not very useful)
- Boards: A "Kanban" board for containers (and the items they contain). Basically an upper level management tool.
- Backlogs: A Heirarchical view of work item containers (and the items they contain)
- Sprints: A Kanban board for the currently work items (PBIs, Tasks and Bugs) that have been assigned to a specific sprint. Basically a low level management tool.
- Navigating away from a page / modal / query discards changes.
- Always click save / close on modal windows
- Click "Save Items" on an updated query / list