Glad you liked it!

It is not very friendly, but I found the way to do it: Condition 1 AND Condition 2 AND Condition 3 OR Condition 1 AND Condition 2 AND Condition 4 Is there an easier way to do it?

Hi. Here is the simplest query. Each one is a query line . *Work item type = user story * state = any * iteration path =@current

Then click on the wrench 🔧 icon Column Options, then select story points on one of the drop downs. Once selected, a column should appear that shows story points

Hi Will, to my knowledge, that doesn't exist with the UI functionality of AzDo. But it doesn't mean that there is not some backend way to do it. 😉

To the right of the search field there is an icon that looks like a checklist. Select that and move through the tabs that pop up. The right most tab should be favorites

Hi. Yes there is. I bring up the query that I need to start with, then I make modifications for the new query. Run the query to make sure it works, finally click the 'Save as' button that is right next to the "Save" button. Now rename the new query. I do suggest to first locate the "save as' button first before you try it. Also it does not hurt to practice this technique on some basic queries that are easy to recreate first. Hope this helps 🙏

@@malpert1000Apologies, Let me explain it right. For ex: I created a query that fetches all work items for Sprint 45. The Query will be: Field* Operator Value Iteration Path = Sprint 45 Let's give this a name "Sprint_Query" Now, Let's say I am creating 20 completely new queries from scratch, and I want to use above already created query in these 20 new queries (basically import query parameters by searching existing query name). Reason of doing is below. Now, If I want to see results of Sprint 44, I won't have to go to those 20 queries to change the parameter, rather I will only change my query "Sprint_Query" and it will reflect in all other queries automatically. Hope this explains.

@@cocofortin I understand. As far as I know, the query ui doesn't offer the ability to make a call to a different query and use that first half of the query in a new query. That would be cool if it did. I know in the test area you have a concept of creating shared steps, but I have not seen this in the query area of devops

@@malpert1000 For which company you are working?

Hi Gustavo. You can manually add any work item as a child to a parent but this goes against the way MS developed Azure to work. So it will not track correctly in the sprint view. Is releases a work item you created manually?

Thanks Ben. As far as I know out of the box, the only thing that could effect it would be 'Effort Hours' in the task. But I don't think it works like that. I think the system simply calculates on new,active and closed to come up with the percentages

You can always add additional fields to any work item, but that field will always be a manual process to keep those fields up to date. We have added a lot of custom fields and they are more a headache then a solution.

Great question. Setting definitions of done can be done on the kanban board View. Once you're on the kanban board View click the gear icon and then go to settings and columns. In that view you can map the different states to the different columns in the kanban board

Not at this time.. but I am always available to help or answer questions

Okay cool. Thanks . Do you know how I can query when things move from one state to another like testing, bugs or any work item type on azure Devops?

I’m looking for a mentor that I can ask questions one in a while. I have experience in what I’m doing . Sometimes I just need confirmation with someone who’s a pro at it .

Please I really need your help. Thanks

@@lindajohnson6983 There are a couple ways to do this. 1) Go to Boards> Work Items>Select 'Recently updated' from the drop down> Select 'Open in Queries'. This will give you a start to a query that you can re-name a modify. Under the 'Editor' tab you will see what the query is querying.. in this case it is on Field 'ID' in @recentProject Activity. You can continue to modify the query as you need. :)

Hi Krishna.. No I have unfortunately not found a way to display the percentages in a widget on the dashboard. One thing you can try is to hide the none needed columns in the backlog view and take a screenshot of it. Or you can use the 'Delivery Plans' option under boards. 1.) Create a project that will show Epics or Features or Both 2.) click on 'settings' 3.) click on 'Fields' 4.) Check 'show child rollup data'. This will show the percentage complete under each Epic and or Feature. You will need to still take a screenshot, but you will also have a timeline as well. hope this helps 😁

​@@malpert1000 Thanks for responding back quickly. I appreciate you putting together this video. I will give this a shot. Happy New Year!!!

Hi Adam.. short answer is yes. Azure Devops comes with out of the box project process templets that allow for issue tracking. Agile(ISSUE), Scrum(IMPEDIMENT), CMMI(RISKS) all have an item that could be used like a risk, but CMMI template actually has the risk item. If your team is already using a template that has one of these items, for another purpose, you and your team could agree on using specific tags to ID risks in that particular work item category. I always suggest to try to use out of the box functionality before you start to add or make custom changes. 😁 Link to MS Template documentation: docs.microsoft.com/en-us/azure/devops/boards/work-items/guidance/choose-process?view=azure-devops&tabs=basic-process

Now that being said... not to go right ahead and start modify Azure DevOps with special work items.. there is that ability. To do this you will need to do the following: 1.)have access level of 'visual studio enterprise subscription' 2) Be in the 'Project Collection Administrators' or higher for the organization 3) At the root level of all the projects click 'Organization settings' 4.) click 'Process' 5.) select a process, click the (...) and select 'Create inherited Process' Note: this new sub-process will now allow you to add and remove new work items. 6.) Click and open the new sub-process you created 7.) you should be dropped into a 'Work item types' screen. 8.) click 'New work item type' and build your new work item. Note 1: to use this new work item, all your projects will need to use this new sub-process as a template, so that you will see the new work item. Note 2: Work with all of your management to identify the new fields for the work item before you start creating . Note 3: Put the risk on the Feature or ''User Story' level of the backlog. Note 4: Come up with a naming convention for your new fields, something that is easy and makes sense. You need to do this because you will later need to be able to query on the fields to build your risk register. I hope this helps 😁

@@malpert1000 Hola cómo hago para que un work item nuevo se pueda identificar en este menú desplegable? de backlog donde se puede ver la estructura de Epic, feature, PBI y lograr ver ese nuevo work item?

Hi @@jennymendez394. Can you ask or respond in English. Sorry my Spanish is rusty

@@malpert1000 jajaj my English is bad but I going to trying explain. I created a new WI but in the backlog I don't found the new WI, I only see epics, features and PBI. Sorry if I wrong in my gramatic

Hi Anik. I would first use the iteration path to query on. Iteration path equal or greater than Dec 1 ,next line, iteration path less than Dec 15 for example. If you don't use iterations.. then use the completion date to query on using greater than and less than operators. Hope this helps 🙏

Hi Sameer. There are a couple of ways. One way is to add a custom field in the work item type that has percentages. This percentage field will need be updated manually. Or another option is to add a 'Add a rollup column' to the backlog. In this option the system will give you percentage complete that is calculated by the system. Steps to turn this on are Go to Backlog> select Column Options> select 'Add a rollup column'> select 'From quick list'> then Progress by all Work Items> click OK. This will then give you a column called Progress by all Work Items and that column will have system generate percentages. I would always suggest to go with what Azure offers and not customizing Azure with special fields. :) I hope this helps

@@malpert1000 thank you so much . One more qs i have if you could help .I am using power bi to show all the test case data .i have one oodata query( query1 )which gives me test case id test plan id test suite id Another odata query i have( query2)which gives me testrun id. I donot find any common filed to link query 1 with query 2 .Can u suggest me how can i do that . I need to show if i have test case1 which was run 10 times so for that particular test case 10 different run ids are created i wanted to show this in my power bi report that test case 1 ran 10 times .

Hi @@sameerkhan-ff8xg unfortunately I do not have experience on Power BI integration. This page talks about fields that you can query on. see Other Fields. I hope this might help. dev.azure.com/LamarCISDInfoServ/LamarIS/_queries/query-edit/abc6cec2-253d-4249-95fd-22e50bec352b/

@@sameerkhan-ff8xg here is another site that might help. docs.microsoft.com/en-us/rest/api/azure/devops/test/Results/Get?view=azure-devops-rest-5.0&viewFallbackFrom=vsts-rest-5.0

@@malpert1000 thank u so very much ..

Right!!!! 😂 smh I’m like what is behind there 👀.

Hey Aman.. I currently I do not have an idea on how to show this cause I have not tried it. I will look into this and hopefully I will have an answer if you are interested

Aman .. I was looking and it looks like Azure only support these field names when using the 'History' field: Changed By, Change Date, Closed Date, Created Date, History, Resolved Date, Rev, Start Change Date, Test Suite Audit, Watermark. Non of these will give us the Changes Iteration Path that is in the History. I think this is because we are suppose to close all user stories at the end of a sprint or start new ones that are related. See docs.microsoft.com/en-us/azure/devops/boards/queries/history-and-auditing?view=azure-devops&tabs=browser

​@@malpert1000 I've had the same problem to track stories that are not complete in a prior sprint. I tag them with the sprint # they have been worked. By doing this I know how many sprints it actually takes to complete a user story and (or) bug without having to dig through the history of iteration path changes. A simple query by the tag can tell me what sprints the user story or bug has been worked on.

@@malpert1000 Hey all. And if you create a tag for each sprint and then tag the US with the tags corresponding to the sprint where it has been? Would that be an option?

Best I can come up with is setting up shared query with Work Item Type = Bug, "state" = New. Although, I believe this will not show new bugs that went from new to and were changed to any other state in the same day (so it's masking a lot of bug open activity that really did happen).