Azure DevOps: work items do not appear in the backlog - azure-devops

I just created a list of work items, under a project in Azure DevOps: 1 epic and 3 features (these 3 are child linked to the epic).
But when I go to the backlogs to see these items, they are not shown. I get the following message:
I tried a couple of solutions that I found on the web, but they do not work.
Please help me to figure out why these are not being shown in the backlog... (of course I'm new at Azure DevOps).
Thanks!

From the screenshot, I can see that only epic and feature:
You need to select epic or feature type in this place:

Create Tasks under the User Story.
Epic ---> Features---> User Story --->Tasks. So then in the backlog top right corner when you select Epic, Features, User Story, Tasks will appear. When you select the Feature, User Story, Tasks will appear. When you select the User Story, Tasks will appear.
Reference link

I found the answer by going through the different buttons on the screen:
Go to Configure Team Settings (when selected a box will be displayed)
Be sure that in the Backlog section all items are selected (in my case they weren´t)
Be sure that all of the work items in different levels are shown by clicking on the + symbol. (the - symbol will hide them).
And that is it!

Related

Empty sprint burndown chart

I'm trying to setup azure devops test project and introduce it to our team. So I created test user stories and related tasks. I also created test sprints (10 work days each) starting with 2021-07-19. So far so good. Taskboard contains tasks and user stories, for test purposed I "finished" some work yesterday. Backlog tab seems to be working well, remaining work and work details works as expected too. Capacity tab is filled.
But once I enter Analytics tab with burndown trend it seems to be empty. No task nor user stories. Did I miss something? I tried all tutorials and all seems to be set correctly. See pictures below.
Do you have any advice or hints?
Thanks!
EDIT: Legacy burndown graph in dashboard works fine.
After a while I found solution. My test project contains only user stories and related tasks and thus the structure is obviously User story -> Tasks. However in the project setting -> Boards - Team configuration I left checked also Features checkbox. Based on that setting expected structure is Feature -> User stories -> Tasks which I haven't. So once I unchecked Features checkbox all started to work as expected. I might be useful for others as well.

Azure DevOps - Can't see many of the work items in backlog

I set up my first AzureDevops organisation by starting with the Agile process but later changed it to CMMI for the organisation to better align with the other projects my team works on. I think this is where the cause of the problem is but can't figure out how to address it.
PROBLEM:
I cannot see in the backlogs any of the Epics I created. The Epic selector in the dropdown menu of the backlog navigation is present and selected. Some of the Features can be seen in the Features backlog, however, not all.
WHAT I TRIED TO DO:
I created a query from the Epics backlog and tried changing its filters and got to see all the epics if I change the filter from having several OR statements on the Area Path filter to one with Area Path Under "top level area path".
I am 100% sure this is because I changed the process. Would appreciate if someone could please let me know some troubleshooting steps to address the issue?
Thank you

Viewing Same stories in different boards

I'm trying to get the same user stories to show up in different boards within the same project. I checked the mapping and everything seems to be ok so I'm not sure what the issue is. Anyone have any suggestions on what to check?
Thanks.
I'm trying to get the same user stories to show up in different boards within the same project.
Azure boards are divided by team and work items are allocated based the Area Path of the team.
To see the same work items in different boards, you could try the following steps.
Step1: Navigate to Project Settings -> Team configuration . Select target teams and check if the teams have the same area path.
Step2: Open the work item that needs to be shared between Boards. Set the area path as the shared area path.
Then you could view the same User Stories in different boards.

vsts How do I add columns to task boards

I have looked at various articles and can see how to add columns to story boards, however we are working in sprints using the task boards and I cannot find any way of adding another column to the task board. Could someone please help me?
Go to the admin for your project. Click the "Process" that you're currently using. Find "Task" in the "Work Item Types" tab. Click the "States" tab and add a new State. This new state will appear as a column on the task board.

Unable to view all backlog items at one place while picking them for a sprint

I still didn't get it.
Where do complete backlog stays if we have to plan for new sprint and pick items from backlog. Like I can see stories/features but what about all bugs/issues, where they can be seen?
I don't want to search for all items in queries/work items. How can I bring all work items in backlog?
Sounds like you're using the Agile template, which doesn't put everything on the product backlog by default. You can edit the backlog settings to put the bug workitem on the backlog. You can find this setting in the Backlog customization screen, as long as Bug is configured to show up as a requirement, it should show up on the product backlog:
Since issues follow a completely different workflow, they cannot be placed on the product backlog. I would guess that they're being used as something else than what they were meant for. But you'd have to help me with additional information. The Issue work item type is the scrum equivalent of an Impediment. Anything that is blocking the team from progressing effectively. These aren't part of the work that goes into the product and are not managed on the same list.
If you're using the Issue work item as a different kind of Bug/Defect then I recommend either creating a custom field on bug to signal the bug type or create a new work item type that is a copy of bug to start with, that way it starts out with all the fields required for it to show up on the backlog.