Bird
Raised Fist0
Azurecloud~5 mins

Azure Boards for tracking - Commands & Configuration

Choose your learning style10 modes available
LearnWhyDeepVisualTryChallengeProjectRecallTime

Start learning this pattern below

Jump into concepts and practice - no test required

or
Recommended
Test this pattern10 questions across easy, medium, and hard to know if this pattern is strong
Introduction
Azure Boards helps teams organize and track their work using tasks, bugs, and features. It solves the problem of keeping everyone on the same page about what needs to be done and what is done.
When you want to track progress on software development tasks with your team.
When you need to report bugs and assign them to team members.
When you want to plan sprints and releases in an organized way.
When you want to visualize work using boards and charts.
When you want to link code changes to work items for better traceability.
Commands
This command creates a new Azure DevOps project named 'example-project' in the specified organization. A project is needed to start tracking work items in Azure Boards.
Terminal
az boards project create --name example-project --organization https://dev.azure.com/exampleorg
Expected OutputExpected
Create project request accepted. Project 'example-project' is being created.
→
--name - Specifies the name of the new project.
→
--organization - Specifies the Azure DevOps organization URL.
This command creates a new work item of type Task with the title 'Setup development environment' in the 'example-project'. Work items represent units of work to track.
Terminal
az boards work-item create --title "Setup development environment" --type Task --project example-project --organization https://dev.azure.com/exampleorg
Expected OutputExpected
Work item 1 created.
→
--title - Sets the title of the work item.
→
--type - Specifies the type of work item, e.g., Task, Bug, Feature.
→
--project - Specifies the project where the work item is created.
This command shows details of the work item with ID 1 to verify it was created correctly.
Terminal
az boards work-item show --id 1 --project example-project --organization https://dev.azure.com/exampleorg
Expected OutputExpected
ID: 1 Title: Setup development environment State: New Type: Task Assigned To: Unassigned
→
--id - Specifies the ID of the work item to show.
This command updates the work item with ID 1 to set its state to Active and assign it to a user. This shows how to change work item status and ownership.
Terminal
az boards work-item update --id 1 --state Active --assigned-to user@example.com --project example-project --organization https://dev.azure.com/exampleorg
Expected OutputExpected
Work item 1 updated.
→
--state - Changes the state of the work item.
→
--assigned-to - Assigns the work item to a user.
This command lists all work items in the project to see the current tasks and their states.
Terminal
az boards work-item list --project example-project --organization https://dev.azure.com/exampleorg
Expected OutputExpected
ID Title State 1 Setup development environment Active
Key Concept

If you remember nothing else from this pattern, remember: Azure Boards lets you create, update, and track work items to organize your team's work clearly.

Common Mistakes
Not specifying the --project flag when creating or updating work items.
Azure CLI needs to know which project to apply the work item commands to, otherwise it fails.
Always include --project with the exact project name in your commands.
Using incorrect work item types like 'task' instead of 'Task' (case sensitive).
Work item types are case sensitive and must match Azure Boards types exactly.
Use the exact work item type names with correct capitalization, e.g., Task, Bug, Feature.
Forgetting to set the organization URL with --organization flag.
The CLI needs to know which Azure DevOps organization to connect to.
Always provide the full organization URL with --organization in every command.
Summary
Create an Azure DevOps project to start tracking work items.
Use az boards work-item create to add tasks, bugs, or features.
Update work items to change their state or assign them to team members.
List and show work items to monitor progress and details.

Practice

(1/5)
1. What is the main purpose of Azure Boards in project management?
easy
A. To host websites and web applications
B. To help teams track work using cards and lists
C. To store large amounts of data securely
D. To manage virtual machines and networks

Solution

  1. Step 1: Understand Azure Boards functionality

    Azure Boards is designed to help teams organize and track their work visually using cards and lists.

  2. Step 2: Compare options with Azure Boards purpose

    Options A, B, and D describe other Azure services, not Azure Boards.

  3. Final Answer:

    To help teams track work using cards and lists -> Option B

  4. Quick Check:

    Azure Boards = Work tracking with cards and lists [OK]
Hint: Azure Boards = tracking work visually with cards [OK]
Common Mistakes:
  • Confusing Azure Boards with Azure Storage
  • Thinking Azure Boards manages infrastructure
  • Mixing Azure Boards with Azure App Services
2. Which of the following is a valid work item type in Azure Boards?
easy
A. User Story
B. Virtual Machine
C. Blob Storage
D. SQL Database

Solution

  1. Step 1: Identify work item types in Azure Boards

    Common work items include User Stories, Bugs, Tasks, and Features.

  2. Step 2: Eliminate unrelated Azure services

    Virtual Machine, Blob Storage, and SQL Database are Azure infrastructure or service types, not work items.

  3. Final Answer:

    User Story -> Option A

  4. Quick Check:

    User Story = valid work item type [OK]
Hint: Work items = User Story, Bug, Task, Feature [OK]
Common Mistakes:
  • Confusing Azure services with work items
  • Selecting infrastructure components as work items
  • Not recognizing User Story as a work item
3. Given a team using Azure Boards, which view shows the prioritized list of work items to be done next?
medium
A. Backlog
B. Dashboard
C. Repository
D. Pipeline

Solution

  1. Step 1: Understand Azure Boards views

    The Backlog view lists work items prioritized for upcoming work.

  2. Step 2: Differentiate other views

    Dashboard shows summary widgets, Repository holds code, Pipeline manages builds and releases.

  3. Final Answer:

    Backlog -> Option A

  4. Quick Check:

    Backlog = prioritized work list [OK]
Hint: Backlog = prioritized work items list [OK]
Common Mistakes:
  • Confusing Dashboard with Backlog
  • Mixing code repository with work tracking
  • Thinking Pipeline shows work priorities
4. A team member cannot see the Azure Board for their project. What is the most likely cause?
medium
A. The Azure Board service is offline
B. They are using the wrong browser
C. Their internet connection is too slow
D. They do not have the correct project permissions

Solution

  1. Step 1: Check common access issues in Azure Boards

    Access to Boards depends on project permissions assigned to users.

  2. Step 2: Evaluate other options

    Azure Boards is a cloud service with high availability, so service offline is unlikely. Internet speed or browser issues usually cause loading delays, not complete invisibility.

  3. Final Answer:

    They do not have the correct project permissions -> Option D

  4. Quick Check:

    Permissions control Board visibility [OK]
Hint: Check user permissions first for Board access issues [OK]
Common Mistakes:
  • Assuming service outage without checking permissions
  • Blaming internet speed for access denial
  • Ignoring permission settings
5. A team wants to track bugs and user stories separately but see both on one board. How can they configure Azure Boards to achieve this?
hard
A. Merge Bugs and User Stories into a single work item type
B. Create two separate projects, one for Bugs and one for User Stories
C. Create separate work item queries for Bugs and User Stories, then add both queries as cards on a single board
D. Use Azure Pipelines to automate bug tracking and user stories

Solution

  1. Step 1: Understand Azure Boards customization

    Azure Boards allows adding multiple queries as card sources on one board to show different work item types together.

  2. Step 2: Evaluate other options

    Creating separate projects splits work and complicates tracking. Azure Pipelines is for automation, not work item display. Merging work item types loses distinction.

  3. Final Answer:

    Create separate work item queries for Bugs and User Stories, then add both queries as cards on a single board -> Option C

  4. Quick Check:

    Use queries to combine work items on one board [OK]
Hint: Use queries to show multiple work types on one board [OK]
Common Mistakes:
  • Splitting work into separate projects unnecessarily
  • Confusing Pipelines with Boards functionality
  • Trying to merge distinct work item types