Adding a Link to a work item breaks my query - azure-devops

We are trying to use VSTS work item management with as few modifications as possible. One of the requirements we have is that our QA department needs to be able to find out which PBIs and Bugs are ready for them to start working.
(we are using our own inherited process based on the built-in SCRUM template)
Our definition of "ready for QA" is that - for e.g. a PBI - all non-QA tasks are done.
I have created this board:
In this case we should be able to make a list (query) that would result in these PBI's and Bugs:
5101 Demo - Ready for QA
4970 Demo - Ready for QA
8542 Bug - Ready for QA
I have made a query that does that (I got help over here)
PROBLEM:
So until we actually started onboarding QA resources, everything was bliss.
However - we have found out that if we make a "link" to PBI's and Bugs they disappear from the result. We need our QA-resources to create a link from their Test cases to the PBI's and bugs and such the query I have does not work anymore.
But - I cannot ... for the love of God ... figure out how to modify my query to enable this. Any references break my query - even between a PBI and a Bug.
What do I do with this?
Problem walk-through:
Before adding references to either PBIs or Bugs the query looks like this:
The query returns two PBIs and one Bug.
Then I add a "Related" link from a Test case to the Bug:
The query now has this result:
Solution found:
The result of the query after the solution proposed by Marina is this:

Please add Work Item Type <> Test case in the linked work item clauses and group the existing clauses:

Related

Show issues instead work items in Sprint's taskboard

I have a azure boards project with simple flow.
We only use Epics / Issues, almost never work-items for sake of simplicity.
Can I customize the Sprint Taskboard (or create new board), so that it will show Issues in the state columns instead workitems?
You can customize the Product backlog Board to do exactly what you want. In which case you could completely ignore the "Sprints":
If needed add additional columns:
To end up with something like this:
You may create a child process based on Agile: Create and manage inherited processes and assign your project to it.
After that, you may assign Issue to any backlog level... as example:
open the task backlog level:
Add issue to the task level:
Use it in the sprint:

Azure DevOps - how to track planned vs unplanned work items

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...)

remaining work by activity as a column or calculated field

I would like to be able to easily see the sum of remaining work (on a Feature) for each activity.
In this example-picture I have a Feature "Keys 0.1" that I would like to add to my sprint. Say I have 60hrs free in the sprint.
At first glance it looks like I can comfortably add the entire feature without any problems. BUT!
Lets say the sprint has room for 20h frontend work and 40h backend work. If that's the case then I cant really add this Feature since it's too much frontend and not enough backend. Our current sollution is to pretty much add stuff, checking if we're fine and removing if we're not.
Is it possible to somehow get "Sum of remaining work Frontend" and "Sum of remaining work Backend" as columns?
One thing I tried was to add 2 new custom fields: "Remaining work Frontend" and "Remaining work Backend". This works fine for the backlog, but when I added tasks to my sprint it didn't use those fields to calculate capacity/remaining time. Does anyone have any ideas of how to get a better overview of how much time something will take grouped by activity?
Get "Sum of remaining work Frontend" and "Sum of remaining work Backend" as columns
Steps:
Open process->select work item type->add new field Create a field Remaining work Frontend and Remaining work Backend(Type: Decimal).
Open Backlog page->Column Options->Add a rollup column->Configure custom rollup->select Roll up as Total and configure the sum column.
In addition, we cannot use these fields to calculate capacity/remaining time.
I hope it can help you.
Update1
We found a similar suggestion ticket. You can add comments in the ticket to describe the feature. To receive the notification about it in time, you can vote and follow this suggestion ticket.
I hope this can help you.

How to create Azure DevOps wiki reports for sprints?

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?

_api/search/query?querytext='Office:Chicago' yildes no results

I have a PROD and DEV farms using the same AD domain.
A query using _api/search/query?querytext='Office:Chicago'&sourceid='b09a7990-05ea-4af9-81ef-edfab16c4e31'
Brings Lots of results from the PROD farm but nothing from the DEV farm and no errors are showing. search on the UI of DEV does find people. but not using 'Office:Chicago'.
What can I do to fix it?
Make sure you can get results using the query in the UI first. Since you can't get results, make sure of some things:
The column's indexed managed property name is correct and the mapping exists
Enough time has passed to be indexed
Do a full index if its been recently added
Items with the tagging exist, and have been crawled
Here are names for OOTB properties: https://technet.microsoft.com/en-us/library/jj219630.aspx