Release Notes
Release Notes: 2026-07-10
Sharper DORA production metrics, cleaner Tech Usage rollups, and steadier Bloomy connections
July 10, 2026
Abloomify Team
2 min read
More accurate production metrics and steadier connections
This release focuses on making the numbers your team relies on read true. DORA now reflects real production deployments even when a single workflow ships to more than one environment, and Bloomy answers engineering questions using that same definition. Alongside it, Tech Usage and Usage Insights get cleaner rollups and smarter defaults, and Bloomy connections to email and external editors complete more reliably.
What's new
More accurate DORA production metrics
Engineering Insights now lets admins tell DORA which deployments count as production when one workflow serves several environments.
- Add a production run-name filter per repository in Engineering Insights preferences, so runs from a single workflow no longer over-count as production ships
- Deployment frequency, lead time, and change failure rate reflect only the runs that match your production definition
- Filters apply on the dashboard and Custom Views right away, with no need to reprocess past data
- Ask Bloomy "what counts as a production deployment for this repository?" and it explains the configured definition the dashboard uses
- Bloomy DORA answers match the dashboard exactly for the repositories you configure
Cleaner Tech Usage and Device Usage Insights
Engineering Tech Usage gets a rollup control, more useful defaults, and clearer charts.
- A new Use subdomains toggle collapses website tools by their root domain across the scope picker, trends, heat map, and top rankings
- Tech Usage opens on the last 7 days and remembers your date range per tab, and loads without pre-selecting a category or tool
- A daily usage view joins shared Top 10, 20, and 50 options on trends and the heat map
- Heat-map tooltips and chart layout are easier to read, including the Device Agent insights section
- Non-productive time now rolls into scoped totals consistently
More reliable Bloomy connections
Connecting Bloomy to your email and to external editors is steadier from setup through daily use.
- Gmail and Outlook connection setup no longer gets stuck on the "Setting up your connection" screen when the confirmation lags
- Email connection health checks are scoped to the right workspace, so connection status reads reliably
- Connecting Bloomy from external editors such as Cursor now completes setup instead of failing partway through
- Editors that check connection details up front can now finish connecting and list Bloomy's tools
Who benefits
- Engineering and delivery leaders: DORA production metrics reflect real production ships, even when one workflow deploys to several environments
- Teams reviewing Tech Usage: website tools roll up by root domain, with a 7-day default and per-tab date memory
- Admins connecting email in Bloomy: Gmail and Outlook setup completes without stalling
- Teams using Bloomy in external editors: connections from tools like Cursor complete reliably
- Anyone asking Bloomy about delivery: engineering answers match the Engineering Insights dashboards
Try it
- Open Engineering Insights preferences and add a production run-name filter for any repository where one workflow ships to more than one environment
- Ask Bloomy "what counts as a production deployment for this repository?" to confirm the configured definition
- Turn on Use subdomains in Tech Usage to collapse website tools by their root domain
- Reconnect Gmail or Outlook in Bloomy if a previous setup stalled
- Add Abloomify MCP access to your external agents, such as Claude, Codex, and Cursor
Abloomify Team
Editorial Team
The collective voice of Abloomify's product, engineering, and customer success teams sharing insights from the frontlines of AI-powered workforce management.