Features and major changes
Updates to historical assignee logic
Flow updated the way ticket metrics are credited to users. This change will improve the accuracy of ticket metrics in workflows where tickets go through multiple assignees during their lifecycle.
Previously, Flow only gave credit for a ticket and its associated metrics to the user who is currently assigned to the ticket. In the case of Sprint movement, that credit was only received by the user who was the assignee at the time the sprint ended.
This change results in crediting a ticket and its associated metrics to all users who were assignees starting at the time when a ticket moves into an Active state. Assignees from when a ticket is in a Not started state or unmapped status will not count toward this logic.
In short, now multiple people can be given credit for the metrics associated with a single ticket. This improves the accuracy for all ticket metrics across multiple workflows. It also means your team composition won’t need to be perfectly accurate to see ticket data. As long as someone on the team worked on the ticket, it will show up in your metrics, even if the current assignee is on a different team or is a shared resource. This simultaneously simplifies your management and increases metric accuracy.
Note: This change affects past and future data for all ticket metrics. This does not include DORA metrics or dev weeks calculations. These metrics already use a version of this logic for their calculation.
Changes you can expect
Generally, expect your number of completed tickets to increase, especially if you commonly reassign tickets at various points in your workflow. Tickets still only count once for a team, regardless of how many assignees on the team are associated with the ticket.
You may see an increase in cycle time, since many tickets that will now be included could represent work with non-team or cross-functional assignees at various parts of the workflow.
You will no longer be required to add the final assignee of a ticket to your team if they’re not already part of it. Now, as long as someone on your team was assigned to a ticket, it will count for the team.
Historically, issues without a current assignee wouldn't count for any team. Now, as long as there was an assignee at some point while the ticket was in an Active or Done state, even if the ticket is currently unassigned, the ticket will count for the team. Tickets that have never been r assigned to a user will not appear in metrics.
Where should I start? There are no new settings or configurations to use for this update. It automatically applies to all your ticket data—no extra steps needed. To make sure your data is as accurate as possible, continue to:
- Configure your ticket projects. Because assignees for tickets in unmapped statuses or a Not started state do not count for metrics calculations, mapping statuses is critical to getting accurate ticket metric data.
- Team curation is easier, but still important. Make sure your teams include all developers on the team. You don’t need to worry about shared resource users as long as someone on the team was an assignee.
Change breakdown by reports
This change affects each report differently. Refer to this chart to understand the changes to which tickets are included in the report.
|Report||Previous logic||New logic|
Only tickets completed in the selected date range where the selected user is the current assignee of the ticket.
Only tickets completed in the selected date range where the selected user was the assignee of the ticket at any point after the ticket moved into an Active or Done state. The user may or may not currently be the assignee of the ticket.
Note: These changes apply only to the Tickets and Story points views. The Dev weeks view is unaffected by this change.
Only tickets/story points completed in the selected date range where any user on the selected team is the current assignee of the ticket.
Only tickets/story points completed in the selected date range where any user on the selected team was the assignee of the ticket at any point after the ticket moved into an Active or Done state. The ticket may or may not be currently assigned to a member of the team. If multiple members of the team were assigned to it, the ticket will still only count once toward the team’s totals. However, the Teams/Team members breakdown would count the ticket multiple times, but no more than once for each nested team/team member listed.
Only tickets completed in the selected date range and projects where any user on the selected team is the current assignee of the ticket.
Only tickets completed in the selected date range and project where any user on the selected team was the assignee of the ticket at any point after the ticket moved into an Active or Done state. The ticket may or may not be currently assigned to a member of the team. If multiple members of the team were assigned to it, the ticket will still only count once toward the team’s totals.
Only tickets assigned to the selected sprints where a member of the selected team was the assignee for the ticket at the time the sprint ended.
Only tickets assigned to the selected sprints where a member of the selected team was the assignee for the ticket at any point after the ticket moved to an Active or Done state. This includes any assignees from after the sprint ends.
Only tickets that currently have assignees that match the filter criteria.
Any ticket, including currently unassigned tickets, that match the filter criteria.
A new look for Team health insights
We’ve updated Team health insights to make it easier to find the metrics you’re interested in. Now there’s a new tab where you can customize your metrics so every time you visit Team health insights, you see the metrics that matter most to you.
We’ve also added additional context on metrics calculations and recommendations so you can more easily understand what the metrics mean and how you can improve them.
Where should I start? Configure which metrics appear in your custom view and explore the new recommendations for additional insights.
Flow resource center
Now it’s easier to stay in-the-loop on new research, features, and training.
We’re excited to announce the new Flow resource center, where you can see what we’ve recently launched, access step-by-step playbooks to use Flow, reference our 20 patterns guide, get notified of special events and live training, and access the newest research from our Developer Success lab.
Where should I start? Click the Flow icon in the bottom right corner when you log in to your homepage to explore the content available to you.
Trend percentages not matching in Review collaboration and Team health insights
Work log showing a blank first column for certain date ranges
Unable to use the team dropdown in reports without the Manage user invites permission
PR metrics for users not matching in Check-in and Team health insights
Some users unable to see targets in Team health insights
Deployment frequency numbers not matching in Team health insights and Retrospective
If you need help, please contact Pluralsight Support.