On Azure DevOps, I have a set of test cases and every test case has a number of related bugs (from 0 to you better not know :p). The link type here is "Tests".
I would like to sort the test cases by number of related bugs, to make an estimation of the most buggy parts of the software.
I've tried but I only found the option "Number of links" ("Nombre de liens associés" in French).
Thanks in advance.
EDIT: we use Azure DevOps Server, not Azure DevOps Service. Thus, unfortunately I can't follow the steps here: https://learn.microsoft.com/en-us/azure/devops/boards/queries/linking-attachments?view=azure-devops#list-items-based-on-linked-dependents
Sort test cases by number of related bugs on Azure DevOps
For this issue , I am afraid it is currently unachievable in azure devops. Currently, there is no feature of sorting by related work items in azure devops.
Running the following query in the azure devops server, you can get all test cases containing related bugs , but you cannot sort these test cases.
Apart from the negative answer, I think what you want is a good idea! So I post a feature request here in DC forum. Anyone interested in this can vote for it and track it. You could vote that suggestion ticket and share your comment there,The product team would provide the updates if they view it.
You can do that only through customization:
Add a new field like Bugs Count or Active Bugs count. Add and manage fields for an inherited process
Create custom app to fill that field with real count of bugs through REST API. Wiql - Query By Wiql, Work Items - Update
Then you can use a column setting to edit the sort order of your query result.
Related
I do quite a lot of security reviews on 365 tenants, which I have made an template. This is all written in a WIKI in DevOps. To that I have an Microsoft Planner this is everything taken out in headlines. This I usually go though with IT.
After that I do an report based on this planner.
But would LOVE to automate this process as the report task is so time consuming and a lot of it is copy paste.
I was thinking of changing my Planner and WIKI out with Work Items in DevOps. This way I could document directly in Work Items what IT is reporting and export the Work Items.
It does however (to my knowledge) not scale that good. It seems to me that I would have to create a DevOps site for every IT department/tenant.
Would love to hear from anybody who have experience with this or related to this.
I have tried with Work Items, but could not make it scalable for more than one IT department.
There is a roadmap feature in JIRA, through which we can create Epics, user stories and assign start and end date to them itself by simply dragging the horizontal bar in table.
With help of this feature we can perform month-wise/day-wise or quarter-wise planning for any project. Additionally, we can export and share with client too. I require this kind of user friendly feature in Azure DevOps too. I tried integrating a Epics and Features Roadmap Plugin, but its not giving precise results as JIRA Roadmap is giving. Its user interface is very confusing, giving some occasional error message. Plus, it configuration is also very tedious and time-consuming. Can I get better user friendly GUI in Azure DevOps for Roadmap creation?
Please Help. Attached screenshots for reference of both platforms feature. Thanks in advance.
DevOps provides Delivery Plans to review the schedule of stories or features your teams plan to deliver. Delivery Plans show the scheduled work items by sprint (iteration path) of selected teams against a calendar view.
If it doesn't meet your requirement, you could check the existing extensions to see whether there are extensions useful:
https://marketplace.visualstudio.com/search?term=roadmap&target=AzureDevOps&category=All%20categories&sortBy=Relevance
I'm fairly new to the different work items available in Azure Devops Server 2020 (TFS) and wonder if I could get some advice on what to select.
I am the only developer in a project and have direct contact with the stakeholder. When the stakeholder report an issue should I then create an Issue/impediment that describes whats is wrong or needs to be changed. And then create a task or bug that I link to that issue/impediment?
You can use Agile Glossary to get some information.
Issues/Impediments:
A type of work item that helps track unplanned activities. Resolving
an issue or impediment requires more work beyond what was scheduled
based on actual requirements.
Bugs:
A type of work item that records a potential source of dissatisfaction
with the product.
You can use Bugs to report issues from your stakeholders and here you also use two ways:
Use bugs on the requirements level and create tasks under it.
Use bugs on tasks level and link them to affected user story or product backlog item.
Show bugs on backlogs and boards
Or you can use user stories/product backlog items as a record to enhance your product.
So I´m looking at the Agile Workflow in Azure DevOps and I´m wondering, what´s the purpose of the Feature work item?
I´ve used Jira a lot and we only used Epics->User Stories->Tasks.
I can´t fine any good explanation to why Microsoft has added this WIT to their default workflow.
See here, Adding Features and Epics
I think of it this way, you would define a feature flag around code for a feature because it's a single shippable unit of testable code, but you wouldn't do the same for an epic because it's a hodgepodge of stories related to a business initiative. Having the two WITs allows you to clearly delineate those two needs and to map the user stories accordingly.
I am having a hard time migrating a tfs2017 update 1 to vsts. I am using microsoft's migration guide however I have managed to migrate a single collection and its users and team account into a vsts account (Dry run), but the issue is I cannot seem to find a way to migrate all the other collections into into that particular account, does anyone have faced situation like this or am I doing something wrong here, Or Is it possible or not, if yes then please throw some light on the possibility.
You can't. VSTS only supports one collection per account.
Your options are as follows:
Combine your existing collections into a single collection, then migrate that collection. This may be more or less difficult depending on the amount of data and history you have, and what amount of that you need to retain, and the fidelity at which you wish to retain it.
There is a concept called Organizations that will allow multiple VSTS accounts to be managed underneath a single umbrella, but it's still in preview.
Per the feature timeline, it's slated for third quarter 2017, so sometime this fall.