Time in State makes it easy to create reports that show how much time each task has been in different stages. When planning a workflow, time is one of the first things we think about. We try to guess how long it will take to finish a task, considering how hard it is and how many resources we have, and then we set deadlines for when we want it to be done.
Using the time in state data, we can compare the time spent on tasks to what we expected. This helps us change our plans during the process if we see that tasks are taking more or less time than we thought.
Here are some questions that time in state can help answer:
- How much time did team members spend on completing some tasks?
- How long do Work Items stay in the “to-do” or “doing” stages?
- How many times has a specific Work Item been in a particular stage?
- How many times does a Work Item move from one stage to another?
How can you calculate this data in Azure DevOps? A popular solution is to export data to Power BI. Almost everyone who works with ADO uses reports in this tool. The disadvantage is that when you integrate another tool to create reports, it takes some time. And in the case of Power BI, it also requires writing code. We want PMs, Team Leads to spend time on analytics, not creating these reports.
The Time in State for Azure DevOps extension by SaaSJet automatically generates reports that answer the above questions. Let’s take a closer look at how it works.
Calculating Time Spent in Azure DevOps (ADO) States
If you want to access detailed reports with calculated information, the Time in State extension for Azure DevOps (ADO) is a helpful tool. It automatically tracks and presents time spent data in an easy-to-analyze format.
The reports available include Time in State per Date, State Count, and Transition Count. One of the most commonly utilized reports is the Time in State report, which reveals Work Items’ duration in each state.
It is also possible to generate a State Count report. It determines how many times a Work Item has been in each state.
Another report available at the moment is Transition Count. This report reveals the frequency of a Work Item being in a specific state.
A significant advantage of the extension for calculating the duration of a Work Item’s stay in a particular state is that the grid has a Smart View mode. It highlights indicators according to their value. The larger the value in terms of time or quantity, the larger and bolder the font will be displayed in the table. This helps to focus on what is essential, avoiding irrelevant information.
Visualizing the Time is State report in ADO
What could be better than charts? It’s a joke, of course, but most users prefer a visual display of reports. It makes information easier to perceive and analyze.
In the Time in State extension, three types of charts are available for reports, as well as a visualization for one single Work Item.
Area Chart
Bar Chart
Pie Chart
Configure Work Calendars to Match Your Requirements
A critical option necessary when analyzing time in states is the ability to customize work calendars. Each company has a different daily routine, weekend schedule, etc.
The Time in State for ADO extension allows you to create several calendars, as part of the team may work remotely and have different terms of cooperation. It is pretty easy to customize a calendar for yourself, and the documentation describes this option in a little more detail.
To sum up
Time in state reports within Azure DevOps (ADO) provide enhanced visibility into your team’s time allocation. By making numerical comparisons, you can conduct a thorough analysis, allowing you to pinpoint the sources of delays. Utilize time in state reports as a tool to recognize and expand upon positive, productivity-enhancing adjustments.
Try it today and achieve all your goals faster!