Previously, in Azure DevOps, query macros like #CurrentIteration used the team context to return their results in the web portal.
Recent changes have changed this behaviour, so that specifying the #CurrentIteration macro now requires a specified team. Whilst i understand the reasons behind this (making the query more predictable, the ability to add multiple team based parameters in a single query), it does mean that it is more or less impossible to create queries that can be shared between teams. Each team has to make a copy, and plug in their own team name.
Is there any way to restore the previous behaviour?
You can create one query with "Or" operators for all the teams:
Related
This is the work progress query i use on Azure DevOps. We have projects in different processes and i chose one project to check the progress and i query across all the projects from a single project. The query goes like this
Work item type, [Any]
And, State, [Any]
And, Assigned to, Team member name
And, Changed Date #StartOfDay('-1d')
Now im trying to make a dashboard with shared queries. Possible solution i could find is to save a shared query separetely for each team member and adding them to the dashboard. But if i have to check friday query results on monday then i have to change the number in last line to 3 for every query. it doesn not seem practical. is there another solution?
I want a query that looks at all team projects whose names begin with "customer". Is that possible or do I have to list them all?
Additionally, is there a way to filter all queries on top of an Azure DevOps dashboard by a common variable?"
I have tried a query but the drop-down for the filter is not available.
Is that possible or do I have to list them all?
You have to list them all. You may use or in groups:
or in for the Team Project field:
We have agile / devops culture -based teams who have a need to track work that has been planned and prioritized at an expected pace, vs work that came in for immediate handling. Some are bugs, some are tasks, some stories, etc.
We're thinking that adding a custom field is the way to go, with potential values of Maintenance and Enhancement. And of course, the hardest part: What would the field name be?
Is there a better approach? We don't think that a new work item is really it, but we could be convinced otherwise.
Additionally, we've looked at all of the canned fields and don't see an obvious field that fits, but we would prefer to use the built-in fields where it makes sense.
What, if any, is the recommended approach? I'd be very surprised if we're the first with this need.
A custom field doesn't have big difference from predefined field, so you can feel free to create one when no existing predefined fields can meet your needs.
I agree with your thought of adding a custom field. As for the field name, we can simply name it PlanStatus,PlannedOrNot or whatever you like...
You only need:
1.One inherited process based on Agile process template.
2.Edit Bug type and create the field.
Then edit other workItem types who also need this field. (Edit=>Add an existing field=>PlanStatus)
3.Then you can create a bug/epic with PlanStatus field and you can use the newly created field in Query. Besides, you can add a widget in Project OverView=>Dashboard to track the planned/unplanned workitems. (Chart for WorkItems widget or Query Results widget or what...)
In Azure DevOps, I need to pull a report of the work done by person in order to distribute payments between team members.
Since the VSTS does not support rollup of the Effort directly:
I suggest you use query to pull out the report of effort for all teams first, then download this report and roll up the effort by person.
Step1: Go Query page, then add Effort column by open Columns Options:
Note: This steps is very import, this can help for pull out a report which contains the Effort field.
Step2: Create a query like below shown:
In the value of State, just input the states which represent the work done in your project. For me, there has 2 states can represent the work has been done: Done and Closed. For Assign to, you could specify the group(s) name which cover the all person you want to check in value blank.
Step3: Download this into CSV by using the button Export to CSV:
Steps4: The above step would generate a excel in local. Then you could apply the Pivot table into that to count the effort by
person.
Sprint 146 in Azure DevOps introduced the possibility to embed queries in the Wiki. More info here: https://learn.microsoft.com/en-us/azure/devops/release-notes/2019/sprint-146-update#embed-azure-boards-query-results-in-wiki
In the image shown in the post:
It shows that you can, probably, create reports for each sprint. I have already some queries that are used to retrieve same data (for example active bugs), but are based on the current iteration like this:
Work Item Type = Bug
AND State Not In Done
AND Iteration Path Under #CurrentIteration
But I'd like to have a report I can see in the wiki for each of the sprint (both past and future ones) I have in the backlog, so how can I achieve that (if there's a way)?
I thought I could create and duplicate the same query replacing #CurrentIteration with the one that I'm interested in, but we're hundreds of sprints in the way, so I cannot create 100 copies of the same query just to replace a parameter.
Is there a simple way to do it? Am I missing something?