Features and major changes
User merge domain preference updates
Now you can choose up to ten preferred domains in your user merge preferences. This lets you decide how additional domains should be merged, and is especially useful for organizations who have users with multiple domains through acquisitions or company renaming. We’ve also updated the auto-merge logic to change the order we prioritize merges to improve merge performance and accuracy.
Where should I start? If you use multiple domains in your organization, take some time to add preferred domains to your user merge preferences to simplify merging in the future.
Ticket project configuration changes
We’ve made two big changes to your ticket project configuration experience. First, we’ve added a Status mapping column to the Ticket projects page so you can identify any projects that have unmapped statuses you should address. Next, we simplified the first page of ticket project configurations so you can more easily include and exclude ticket types from ingestion.
Where should I start? Take a look at your Ticket projects page. If any of your ticket projects say Unmapped status in the Status mapping column, take some time to finish configuring your project by mapping the statuses so your ticket data is the most accurate.
Domain mapping functionality for reverse proxy support
Some customers use reverse proxies in front of their self-hosted git or ticket servers, which can make correctly ingesting data difficult without customer configuration to map public URLs to private URLs. Now, Flow can handle the domain mapping for you.
Where should I start? If you have a self-hosted git or ticket server behind a reverse proxy, reach out to your Flow contact for information on how to get your domains mapped in Flow’s system. You’ll need to let us know the fully-qualified domain name of your public domain in the form of public.domain.com. You can also provide a port number as needed.
Resolved issues
- Custom date range doesn't persist when changing filters on Home
- Tickets included in Dev weeks for a user when they did not contribute to the ticket
- Links from Investment profile to Ticket log doesn't include historical assignees on the Ticket log list
- Unable to bulk include users in metrics
- Unable to view Lead time for changes in Retrospective
- Unable to access the Collaboration metrics API
- Unable to see DORA metrics for parent teams
- Unable to use some RegEx syntax for deployment inclusion rules