I have a DevOps account with a project in it. I am using the Agile process. I have work items such as bugs, features, etc. Please notice that I can actually see bugs in my KanBan board as I did the configuration to show bugs in there.
Problem
Problem is that if my bugs have the root area MyArea, they are shown in the board, but if I set a subarea MyArea/Subarea, the bug disappears from the board.
How do I solve this?
That`s may depend on your team settings. As example, you can enable sub-areas in your root area:
Or add every every area to the team areas that you want to see on your board.
Related
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
Host Details:
OS Editon: Azure Devops server 2016
OS Build: 1607
Azure DevOps Details:
AZ server: 2019
The issue:
For one Team Project, we are requiring to have three different sub-area paths so we can place work accordingly for each team Properly to follow it.
The three sub-areas were created as follow:
and visible are visible from Bords:
But, and here the issue, the Button for creating New Work Item now is Disabled, as shown below:
Also
How could re-enable this button?
We use this button at daily basis to create New Tasks or as required, is so weird that enabling one functionality we lost other.
It’s possible your workflow has the work item disabled. Check your process and see if the work item type is disabled. Also on the ribbon next to View as Board, hover and click, it will give you a more detailed error message.
If the work item is disabled you will see this message.
Solved by myself
Hello Martin, thanks for reaching me out so swiftly,
I did found the issue, due to a lack in Azure DevOps documentation didn't know that when creating a new Team Project have to create the extra teams within the Project before anything else, and then is that can proceed to add define the sub-area paths in the Boards Section and then is when is possible to have First multiple teams within a team project and Second have enabled the Work Items Button for each team sprint:
See for example this MS official documentation how they don't make any clarification of it: {{ https://learn.microsoft.com/en-us/azure/devops/organizations/settings/about-areas-iterations?view=azure-devops }} :
Also here {{ https://learn.microsoft.com/en-us/azure/devops/organizations/settings/set-area-paths?view=azure-devops&tabs=browser }} :
So MS docs miss that point completaly!
Solved each team is an independent unit and for that each will have their own setup,
Once that is corrected all works fine
I have been tasked with running point on implementing Azure DevOps on my team at work.
We are using the CMMI process and tracking bugs at the requirement level.
Recently, it was brought to my attention that when we marked a Bug work item as active, manually change the state and not drag the card to the next swimlane, it simply disappears from the board. The work item can still be viewed on the task board, but is no where to be found on the requirements board until the state is changed again.
Has anyone else run into this problem and know of a fix?
Thanks
The issue is the configuration of the board itself. The default does not include bugs, so when you create your columns, the bug configuration for "Develop" gets set incorrectly.
Go to your settings for your board by clicking the gear icon in the upper-right of the board
Once into the settings, choose "Columns" from the list of items on the left of the modal window and then choose the column where the Bug items keep disappearing (the Develop column in my case), and you'll see some drop-downs for Bugs and Stories for "State Mapping".
If you change the bug setting here to "Active" and then save, the bugs should reappear on your Develop board. You'll want to do the same check for any other columns.
You can update Working with bugs setting for boards to Bugs are managed with tasks.
You will need team administrator or a project administrator permissions to change this setting:
I want to create a custom kanban board based on a new query for my team.
The ones you get by default seem to be an all or nothing thing, we would like to break down our work outside of sprint planning in to "feature boards" that contain items that may span multiple sprints but are towards a common sub goal of our project.
Is this possible?
That's not the common scenario which TFS/Azure-Devops designed for.
Based on your requirement, you can try creating multiple teams and areas. Area paths allow you to group work items by team, product, or feature area. Then set team default to select the areas the specific team owns below. The selected area paths will determine what shows up on your team's backlog/board and what work items your team is responsible for.
Please see below articles for more information:
Kanban basics
Set team defaults
About area and iteration paths (aka sprints)
Besides, you can also try this extension: Kanban Board Tools, it provides a set of tools to enhance Kanban board usage within TFS and VSTS.
You might want to take a look at this free extension: https://marketplace.visualstudio.com/items?itemName=realdolmen.querybasedboards, that allows you to display a query result into columns, based on work item states configuration.
Still new to VSTS. Sometimes work or requests come in and our team needs a way of sorting these into areas that will become projects, but not immediately. Can I create a task without first creating a new team project?
Also, is there a way to see different projects at a higher level than the tasks in one view on a kanban board? Ive seen some delp docs on dashboards etc, but everything including tasks are all scoped to a team project. While this makes sense to have these things for a project, but what about higher level views? At any one time, there might be 4-5 different projects being worked on as well as 2-3 different things that are not part of a project yet. Maybe VSTS isnt the place for these more general items, but a generic kanban board?
The term "team project" is kind of an antiquated name that doesn't do a great job of accurately describing its purpose. Think of a "team project" as a portfolio of related applications rather than something for a single team, or a single project.
The most common way to address is this to keep everything in a single team project. There are a lot of things that don't cross team project boundaries, and trying to force that behavior is a recipe for frustration.
Within a team project, you can create Teams. Each team can have its own backlog, its own iteration schedule, etc. Teams are assigned an area path that they own. If a work item is under their area, it's assigned to that Team.
If you have Team A's area path set to FooProject/Team A, then it belongs to that team. A work item under FooProject/Team A shows up on that Team's backlog.
From there, you can adjust security permissions and such so that if a person isn't a member of a given Team, they don't have access to see or manipulate other teams' work items.