Features and major changes
Knowledge sharing report
Later this month, the Knowledge sharing report will be removed from the left-hand navigation.
To make sure the valuable insights from Knowledge sharing are still available for you, the Sharing index is now available as a metric in Team health insights and Review collaboration. Plus, we've added the Review radar to Review collaboration to use alongside the Collaboration map. These additions will help you get a more thorough picture of the collaboration patterns in your teams.
As part of this update, teams with high levels of PR collaboration outside their team might notice a change in their Sharing index due to minor changes in the underlying calculation to align with the PR logic in Review collaboration and Team health insights.
Where should I start? If you’re already familiar with the Review radar and Sharing index, keep using them and incorporate them with your use of Team health insights and Review collaboration. If the Sharing index and Review radar are new to you, consider adding them to your team discussions to better visualize how you’re working together to complete reviews.
DORA for ADO
Now you can set up incident configurations for ADO services integrations. This means that all four DORA metrics are available if you have an ADO services integration.
Where should I start? Set up an incident configuration for your integration and learn more about Change failure rate and Time to restore service to understand how your data will appear in Flow.
Historical assignees in Sprint movement
Now when you hover over the Assignee column in Sprint movement, you can see all historical assignees associated with a ticket, not just the current assignee.
Where should I start? If you’re ever not sure why a ticket or sprint is associated with a particular team, hover over the Assignee column to see if a team member was ever assigned to the ticket in an active state. This would count the ticket toward all of their ticket metrics.
Miscellaneous updates and changes
- We’ve updated the minimum recommended version of our Azure DevOps Server (TFS) integration to Azure DevOps Server 2019. Because of the underlying API update needed to processes this data, you may notice users ingested from your integration having an email address of the form
user-456@123.id.gitprime.comwhere 123 is the integration ID and 456 is the vendor-provided user ID. Make sure these users are merged correctly to see accurate data in Flow. - We’ve updated tooltips in several reports so they behave consistently across Flow and you only need to hover over them to access them.
Resolved issues
- Unable to save regex for configuring deployments
- Bitbucket server repos with a username and password integration not updating
- Corrected average versus median labels for DORA metrics
- Unable to enable and disable the deployment source for repos
- Unable to view tickets by investment layer from Investment profile
- Resolved issue with apex user filters in the Pull request API