I would like to be able to have the issues and tasks of the different projects in Azure shown in one sprint planning overview.
We are with a small team but multipele projects. so we work on them simultaniouslly
Currently there is no direct way to show all the workitems across projects in one sprint planning overview.
You could merge all projects into one azure devops project and use area paths to differentiate them. Area paths is designed to allow you to group work items by team, product, or feature area. But you can also define different area path for each of the project to group the workitems from different projects. Please check the document About area and iteration paths, and document Define area paths and assign to a team
You can also define different team for each of the projects to differentiate them in one azure devops project(One team for one project). Please check the document about Teams, and the tutorial to add a Team.
Then you can view the workitems of different projects by filtering the area path or team in azure devops Boards, Backlogs and Sprints. Below screenshot for below example:
Another workaround which allows to view all the workitems across multiple project is to use Queries. check Query across projects shown as below screenshot. Please check tutorial Query across projects
Related
Since the process of one A/B test usually takes multiple sprints I would like to add another board in which I can add the A/B tests (as F.E. features). User stories for one sprint can then be added to a specific sprint for my team (which consists of a few specialists and a developer). This way I am able to overview the status (research phase, test , code writing, running, analysis, etc.) of all tests in one overview. I have not been able to find out how this is possiblie within Azure Devops, or if there is a work around. Can anyone help me?
My team also works in projects other than A/B tests, which means we cannot use the boards section.
Unless there is a hidden way to add another board to a team?
You could Copy or clone a work item to add the user stories or tests to a new boards. Open the user story you want to clone, then click Create copy of work item and choose whether to include exist links, attachments and child work items. After creating, change the Area and Iteration to your target boards.
Update
In Azure DevOps you can only create boards by creating a team. The team board is created as a side-effect of creating the team. Please refer to Manage and configure team tools and Configure and customize Azure Boardsfor details.
After creating and configuring a new team, you could see the boards in the dropdown list.
Is there a possibility to track Work Items in Azure DevOps "Cross Project" wide?
So that I can get an overview over all e.g. Epics from all Projects and when they are due. (Cross Project Roadmap for specific work items).
I searched the extention Library and thought it might be able to do it over the API by pulling all work items and then combine it in an own tool.
Any Ideas would be appreciated.
You can create a query and and mark the "Query across projects" checkbox, then you will get a results from all the projects.
For example, a query for all done Epics in all the projects:
In this way you can query each work item field, save the queries and put the results on the dashboard, so you will have "cross projects roadmap".
Update on this Issue. The Azure DevOps Extention https://marketplace.visualstudio.com/items?itemName=ms-devlabs.workitem-feature-timeline-extension does basically what is needed. Not completely but in some sort.
I have a requirement to split one big Team project in Azure DevOps to multiple team projects, as you know there are work items, iteration , repositories, test plans and CI/CD pipelines to move across. What is the best way of achieving this - apart from manually moving them across ?
Currently, there is no default way to move sources from one Team project to another. You can check OpsHub Visual Studio Online Migration Utility which can migrate source code, work items, etc.
Meanwhile, there are move work items (select some work items > Right click > Move) to another team project, move git repositories between team projects, move items in TFVC features that can help move sources.
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.