I have problem with configuration of AzureDevOps process.
My goal is simply automate work items - when work item changes state to done or is in state done on certain board I want to transfer it on other board.
I tried to achieve this by applying custom rules in my organization. Example:
I navigate to Organization Settings, select Process then I select process from list (is inherited from Scrum parent). Then I select bug (for example) and go to rules tab.
Here is screen of my configuration
Both Board no.1 and Board no.2 exist as Team Projects. I've added clearing assign to field and this one works properly.
I wondering if there is much easier way to automate moving work items through boards or team projects on status change.
I wondering if there is much easier way to automate moving work items
through boards or team projects on status change.
For this issue, I am afraid there is no easier way to achieve this requirement. Azure Devops has provided a built-in custom rule function to achieve this. This is already a very easy way.
In addition, we can also achieve this through the azure logic app, but this needs to be set in the azure portal. I don’t think it will be more convenient than custom rules.
To move work items to another project, you must be a member of the Project Administrators group or be granted explicit permissions to move work items.
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.
We've been using environments for a while now for our dev and test instances. I like being able to go to the environment and seeing the commits and work items associated with the particular build/release but can't find a way to export them. Does anyone know of a way to export the workitems?
Using environments you also loose the ability to see which build/release a ticket went out in or have I missed something?
Your first and second question, kind of, have the same answer.
In short, you don't want to be using Environments to view which work items are associated with a release.
Azure DevOps has a built-in mechanism to view work items directly within the Release or Pipelines page (Depending on whether you're using classic or YAML).
Here is a great guide published by Microsoft regarding how work pipeline-based work item linking works, as well as how to retrieve work items associated with a release:
https://devblogs.microsoft.com/premier-developer/how-to-retrieve-all-work-items-associated-with-a-release-pipeline-using-azure-devops-api/
Update:
Specifically regarding how to view linked work items in Pipelines. You'll want to look under "Related":
Clicking on "x work items" will show you the full list of work items:
I'm trying to configure and customize the Azure DevOps tool as per the requirement for my application development team. In the boards setting, I have selected the option "Bugs are managed with Tasks" to get a good view of my sprint items. However, my team reports post production issues as Bugs in the tool and enabling the above mentioned setting doesn't allow me to view these Bugs in the Kanban Boad. Reason is they are not linked with any User Story.
I have been exploring the options in Backlog levels options available in the Processes settings and found that the Backlog level "Stories" is tagged only for User Story.
My query here is can i try linking Bug and Task to the already existing "Stories" backlog level. Azure DevOps does gives option to create a custom backlog level and custom Work item type. I would like to customize the existing functionality to best fit my team. Please let me know if there is a work around.
Query regarding Backlog Levels in Azure Devops
This behavior is by designed and there is no way to fix it at present for the exists Work item type Bug.
Because there is only one requirement backlog and it cannot be removed, but can be renamed and edited:
There is an user voice about this request on the Developer Community.
As workaround, we could create a custom the Work item type and add it to backlog level, for example, I create a custom Work item type BugWithoutTask, then add it portfolio backlog:
Then go to backlog settings and enable new backlog:
Now, we could these BugwithoutTask in the Kanban Boad:
You could check this document for some more deails.
Hope this helps.
I am working as a Product Owner for a development team using scrum, we are using VSTS for our backlog.
So far I have been organizing my backlog using Epics and Features, I am mainly using features.
I use Features both to group work items but also for keeping control of delivering stuff. If I for instance know that I need to deliver a certain functionality a certain day then I create a Feature for that and include the needed work items. I need to do that because I manage many projects simultaneously.
So far, so good.
But now Product Management want to start creating Epics and Features for them to organize work. I can live without the Epics, and it is fine that they create the features and I add work items. But when I start executing I need some way to organize into deliverables.
Any idea how I can do that, basically I need a group like features but in between feature and work item
You can add tags for your and other Epics to distinguish them...
basically I need a group like features but in between feature and work item
Alternatively you can create a new work item type like features. Please see Customize a project using an inherited process for details.
Create an inherited process
Custom the process
Add a new work item type
...
Apply the customized process to your project
UPDATE:
You need to add a new Portfolio backlog level, but in Azure DevOps (VSTS) the new Portfolio backlogs can only be added as the top level, that means the hierarchy should be Deliverable > Epic > Feature > Backlog Item.
So, in this case you can rename them to match your requirements, for example rename Feature to Deliverable, Epic to Feature, Deliverable to Epic...
Please see Customize your backlogs or boards for details.
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.