What determines what shows up in Azure Devops backlog?

1
votes

I am using Azure DevOps Server Version Dev17.M153.3 - self-hosted Azure DevOps.

I have tried but can't figure out what are the rules for what items show up in the backlog. The backlog configuration is to see only User Stories.

Let's say my Team is "DevOps." I have drag/dropped several User Stories and child Tasks onto "DevOps Team Backlog" and then I go to the Backlog sprint and they are not there, but 2 random tasks are, that have

Area: DevOps, Iteration: DevOps\Some Product\Some Sprint

I can go find the items I drag/dropped onto the backlog under Work Items, and they have

Area: DevOps, Iteration: DevOps

If I use the "Create Query" function on the backlog, the query is

Work Item Type: User Story, Area: DevOps, Iteration: DevOps, State: New,Active,Resolved

and many items show up, which is what I expect to see in the Backlog view.

What are the rules to determine what shows up in my team's backlog view?

1
tfsazure-devops
Did you start by reading the documentation on how backlogs work? – Daniel Mann
@DanielMann Yes, I'm sure it's in there somewhere but nothing jumps out at me as something I'm doing wrong. My Backlog Iteration is setup as "DevOps" in this example. – user210757
Embarrassingly, part of my problem was I had a search filter set in my backlog. – user210757
Make sure the Stories you want in your team backlog are in the Teams's area path. If not they will not show up on the backlog. – Etienne

1 Answers

0
votes
  1. You use backlogs (user stories) to define your future work.

enter image description here

  1. You plan your next iteration by assign user stories to that iteration in the backlog

enter image description here

  1. You create child tasks in the sprint backlog

    enter image description here

Additional links:

  1. Organize your backlog, map child work items to parents
  2. Assign backlog items to a sprint
  3. Add tasks to backlog items