I am using power automate for Azure DevOps integration. Here is what I want to achieve. I want to create a new work item when an email arrives in a project but in a specific Area Path for the team.
I am providing Area Path and Iteration Path in my flow configuration, but when the flow triggers, it creates work item both in Project Backlog and Area Path backlog, where as I only want it to create the issue in the specific Area Path.
Can someone kindly help? Thanks, Bee
At the moment, here is how I resolved this duplication issue.
Provide all the necessary configuration in your workflow.
Include your area-path in the workflow
Provide a unique parent-id you want to link your work-item. Feature or an EPIC.
Seen the screenshot below.
After I provide a unique parent/child relationship, it stopped creating duplicate backlog items in my Project backlog and area path backlog.
Hope this helps everyone.
Thank you
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.
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
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.
in Azure DevOps, is there a way to generate a report so you can see Cumulative flow diagram (CFD) by Area Path as oppose to Team?
We are using Azure DevOps (CMMI, Kanban) for our work. In our AzureDevops configuration, we have two teams (to make it simple, I will call it Team A and Team B). Under each team, we have broken up the work into sub-teams using Area Paths. For example, Team A is IT Operations Team and the Area Path represents IT Operations sub-teams (e.g., Network Team, Help Desk, Linux Server Support, etc.). Our Team B is Line of Biz applications and the sub-teams are aligned by technology (e.g., DBA, CRM, etc).
The CFD Widget in Azure Devops doesn't allow you to view the CFD by the Area Path, it will just view it at the AzureDEvops Team level (Team A or Team B).
It looks like the CFD widget is out of the question, is there an alternate way to gather CFD information by Area Path in AzureDevops?
Thanks in advance for your help.
I am afraid Azure Devops doesn't support viewing the CFD by the Area Path currently.
However, As a workaround you can create a Query to filter the work items by area path and then create a Chart similar to CFD and add to the dashboard. See below example:
1, Create a Query in the Queries section to filter the work items by area path.
2, Go the Charts tab, Click New chart, Choose the Stacked area chart type, Choose Stack by State.
Another workaround is to create new teams for each sub-team(ie. Network Team, Help Desk, Linux Server Support, etc.). Then select the sub area path in the Team Configuration page for these new teams.
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.