Release Notes

Better control for engineering reviews and integration scope

This release makes it easier for engineering leaders to review work through the lens that matters most to them. Teams can now compare custom groups inside the engineering dashboard, follow task velocity with clearer task context, and keep integration-driven task views cleaner by excluding repositories or projects that add noise.

What's new

Compare performance using custom engineering groups

Engineering leaders can now define and use custom groups in the dashboard so review conversations map more closely to how their teams actually operate.

• Filter dashboard views by custom engineering groups
• Compare groups side by side during operating reviews
• See contributor and group metrics in a structure that better matches your org

Task velocity views are easier to follow

Task velocity drill-down is now more useful when teams need to understand where work is moving and what each item connects back to.

• Follow task details with clearer connected-tool context when available
• Review task velocity with cleaner filtering and less ambiguity in drill-down views
• Make engineering review conversations faster when teams need to inspect the work behind the metric

Exclude noisy projects and repositories from task-related flows

Admins now have more control over what gets included from supported integrations.

• Exclude specific repositories or projects when they should not shape task-related views
• Keep dashboards and related workflows focused on the work that matters
• Reduce noise for teams that need cleaner engineering signals

Small UI consistency improvements

A few touched views now handle empty values more consistently.

• Missing values are easier to scan in tables and cards
• Teams get a cleaner dashboard experience during quick reviews

Who benefits

• Engineering leaders: more flexible comparisons and clearer review workflows
• Admins: better control over integration scope for task-related data
• Delivery and operations teams: cleaner, more focused engineering signals

Try it

• Open the Engineering Dashboard and compare custom groups
• Drill into Task Velocity to inspect work with clearer context
• Update supported integration settings to exclude projects or repositories that should stay out of task-related views

Faster device-agent discovery for admins

This release gives company admins a simpler way to check for newly discovered device agents without waiting on a separate backend process. It also makes the process easier to follow from start to finish.

What's new

Admins can check for new device agents on demand

You can now trigger a new device-agent check directly from the Device Agents settings page.

• Start a check when you need it instead of waiting for a separate process to run
• Use it after setup changes when you want quicker confirmation that everything is connected properly
• Keep the workflow inside the product instead of relying on support follow-up for basic validation

Progress stays visible in the history view

The existing history view now gives a clearer picture of what is happening while the check runs.

• Follow progress in the same place your team already uses for device-agent history
• See the run without jumping between separate tracking surfaces
• Confirm that the sync completed with less guesswork

The experience is more self-serve and easier to validate

This update is designed to reduce friction for admins who are setting up, reviewing, or troubleshooting device coverage.

• Validate changes faster after connecting or updating a device source
• Give operations and support teams a clearer record of what was checked
• Reduce back and forth when you just need to confirm that discovery ran successfully

Who benefits

• Company admins: faster manual checks and clearer validation after setup changes
• Operations teams: better visibility into device discovery progress
• Support and rollout teams: easier confirmation when helping customers verify new device coverage

Try it

• Open Device Agents in settings
• Run Check for new device agents
• Watch the progress in the history view until the run completes

More focused engineering views, more precise access control, and clearer insight dashboards

This release gives engineering leaders more control over how they read delivery data, helps admins grant page access with more precision, and makes key insight views easier to scan and trust.

What's new

Engineering teams can filter velocity views by project

Engineering dashboards now make it easier to focus on the work that matters most for a given product, initiative, or codebase.

• Use task project filters to narrow velocity views to the projects you actually want to review
• Keep contributor and throughput views aligned around the same scoped work instead of mixing unrelated activity
• Configure dashboard preferences with clearer defaults so repeat reviews feel more consistent week to week

Review health has a deeper repository view

Teams can now move from a high-level review health signal into repository-level detail when they need to understand where review load or friction is building.

• Open a repository breakdown view to see which repos are driving review activity
• Get a clearer picture of approval patterns and change-request behavior during code review
• Use sharper cycle time and velocity views to support standups, retros, and planning with more confidence

Admins can grant page access with more precision

Access rules now support more flexible targeting, so admins can share the right views with the right people without relying on broad company-wide access.

• Grant access to specific employees when a role-wide grant would be too broad
• Extend access using teams, departments, or divisions so reporting views can match how the company is actually organized
• Manage these options in cleaner access flows that reduce setup friction when permissions need to change

Productivity and device insight views are easier to read

Several insight surfaces now present information more clearly, helping leaders spot trends and outliers faster.

• Productivity views are easier to scan when comparing groups and time periods
• Device insight layouts are more polished and easier to work through during operational reviews
• Updated visual structure helps teams move from trend spotting to action with less hunting around

Who benefits

• Engineering leaders: project-scoped velocity views, better review health detail, and clearer delivery signals
• Admins and operations leads: more precise page access controls for people and org groups
• Managers reviewing productivity trends: cleaner insight views with easier comparisons
• Teams running weekly operating reviews: faster access to the specific signals they need

Try it

• Open the Engineering dashboard and apply a task project filter before your next delivery review
• Use the review health repository view to spot where approvals or change requests are piling up
• Update page viewing permissions for a specific employee, team, department, or division
• Revisit productivity and device insight pages to compare the refreshed layouts in your normal reporting flow

Engineering velocity, smarter permissions, and a cleaner subscription experience

This release shifts the engineering dashboard from burndown to a full task velocity view, gives admins more granular control over Capacity & Usage access, and makes the subscription blocked experience clearer for everyone on the team.

What's new

Engineering dashboard now shows task velocity

The engineering dashboard replaces the legacy burndown chart with a dedicated Task Velocity card and a drill-in dialog so engineering leaders can track throughput across sources without relying on a single burndown-only view.

• See how tasks are moving across Jira, GitHub, and Linear in a single velocity view
• Filter by source and status directly in the card to focus on what matters
• Open the detail dialog to drill into per-period breakdowns, top projects, and individual task records
• Cycle time charts now surface median alongside average, with safer edge-case handling and richer tooltips including PR labels, so standup and review conversations start from numbers teams trust

Capacity & Usage permissions are more granular

Admins can now grant a Self View permission for Capacity & Usage, letting managers include their own data alongside their team's view without giving them full company-wide visibility.

• Grant managers access to their own data separately from their team's reporting chain
• The Roles & Permissions drawer groups related Capacity & Usage view options under one expandable row so all the variants are easier to find and configure
• Permission changes do not affect the underlying page or routing structure, keeping rollout risk low

Subscription blocked states are clearer and recovery is faster

Teams on inactive paid subscriptions now see focused guidance instead of landing in a confusing sign-up or access loop.

• Company admins are taken directly to the renewal path when action is needed, so the whole team's access can be restored faster
• Team members who are blocked see their admin's contact information inside the product so they know exactly who to reach
• Subscription status is enforced more consistently across sign-in and access paths, reducing the chance of billing and access states drifting apart

Integrations onboarding is tidier

The legacy GitHub connector has been removed from company-facing onboarding and the integrations catalog so admins only see actively supported integration options.

• The unsupported legacy GitHub option no longer appears during onboarding or in the integrations list
• Visibility is controlled from a single source of truth, so the option cannot reappear from stale provider data

Who benefits

• Engineering leaders: velocity-first dashboard with drill-in detail and trustworthy cycle time medians
• Admins managing access: a new Self View option and a cleaner grouped permissions drawer for Capacity & Usage
• Teams on inactive subscriptions: clearer blocked state messages and faster recovery paths for both admins and team members
• Admins configuring integrations: onboarding only shows supported connectors, reducing confusion during setup

Try it

• Open the Engineering dashboard and switch to the Task Velocity card to explore throughput across your connected sources
• Drill into a period from the detail dialog to see which tasks moved and which projects drove the most velocity
• Navigate to Roles & Permissions and look for the grouped Capacity & Usage row to configure Self View for relevant managers
• If your team recently lapsed on a subscription, re-sign in to see the updated guidance and renewal path

Bloomy answers CRM questions live, and your pipeline view just got a lot richer

This release brings live Salesforce and HubSpot data into Bloomy, gives revenue leaders a more powerful way to explore ARR trends, and keeps productivity metrics current with nightly AI labeling.

What's new

Bloomy can now answer live CRM questions

Bloomy connects directly to your Salesforce or HubSpot data so you can ask about deals, accounts, contacts, and pipelines in plain language without switching tabs or pulling reports.

• Ask about open deals, pipeline stages, contact history, and account timelines directly in chat
• Bloomy surfaces deal contacts even when standard contact roles are missing, using account contacts and recent email activity as fallbacks
• Pipeline stages are richer and include more context, so summaries reflect how your team actually sells
• Bloomy picks the right CRM source automatically when more than one integration is connected

RevOps pipeline view is more informative

Revenue leaders and RevOps teams have a clearer, more interactive way to explore performance and ARR trends without leaving the overview.

• Pipeline chips use clearer colors so you can scan stage mix faster
• Click any ARR KPI tile to open a detailed trend panel showing won and lost amounts, average ACV, open pipeline, and win rate
• Drill into any period directly from the trend panel to see which deals closed, sorted by amount
• Closed deals carry pipeline metadata so historical performance comparisons are more accurate

Nightly AI labeling keeps productivity data current

The device pipeline now runs an auto-labeling pass every night so newly discovered apps and URLs are categorized without waiting for a manual review cycle.

• Unlabeled apps and URLs are categorized automatically each night using AI
• Labels include category, reasoning, and a system actor attribution so the history stays traceable
• The existing manual review and labeling flows are unchanged

Bloomy sources are easier to read

When Bloomy draws from multiple documents or integrations, the source chips are now easier to scan and more accurately reflect where the answer came from.

• Provider names are normalized so duplicate or inconsistent labels are cleaned up
• Transcript-backed sources are detected from document metadata and shown more accurately

Who benefits

• Revenue and RevOps teams: live CRM answers in Bloomy and richer pipeline exploration without leaving the product
• Sales leaders: ARR trend drill-downs and closed-deal details make period reviews faster
• Admins managing integrations: CRM connections are easier to configure and the multi-connection experience is more predictable
• Teams tracking productivity: nightly labeling keeps app and URL categories current with no manual effort

Try it

• Open Bloomy and ask about a specific deal, account, or pipeline in your connected CRM
• Navigate to the RevOps overview and click an ARR KPI tile to explore the trend panel
• Drill into a recent period to see which deals closed and compare against prior periods
• Check your device agent productivity view and look for newly labeled apps or URLs from the past week

Better setup guidance, stronger agent controls, and cleaner matching flows

This release helps teams connect Salesforce with less guesswork, manage device agents more confidently, and move through matching and employee cleanup workflows with better visibility.

What's new

Salesforce setup is easier to follow

Connecting Salesforce now feels more guided from the start, especially for teams handling setup for the first time.

• A clearer install-first flow helps teams understand what needs to happen before they connect
• In-product guidance makes it easier to find the setup steps and troubleshoot common connection issues
• Salesforce settings are easier to review in context once the integration is in place

Device agent management gives admins more control

Admins now have better tools to keep device agent lists clean and relevant.

• Device agent views are more capable and easier to work with
• Teams can use keyword-based auto-archive controls to reduce clutter from irrelevant agents
• Unarchive actions make it easier to bring back the right agents when activity resumes

Matching flows are easier to trust

User and device matching surfaces now do a better job of helping admins make the right decision without extra cleanup afterward.

• Matching flows make room for creating an employee when one does not already exist
• Validation and processing feedback are clearer during matching steps
• GitHub outside collaborators are easier to spot in matching views

Employee cleanup feels safer

When admins remove an employee, connected screens now stay in sync more reliably so the result is easier to understand.

• Deletion behavior is clearer across dialogs and tables
• Follow-up updates feel more immediate after the action is complete

Who benefits

• Revenue and ops teams using Salesforce: setup is easier to follow and troubleshoot
• Admins managing integrations: connection and settings flows feel clearer
• Teams with large device inventories: agent cleanup and recovery are easier to manage
• People ops and IT admins: matching and employee management workflows feel safer and more transparent

Try it

• Connect Salesforce in a workspace that has not completed setup yet and review the new guidance flow
• Open device agent management and test keyword-based cleanup controls on a small set first
• Run through a user matching flow and confirm outside collaborators and create-employee paths are easier to review
• Remove a test employee and verify related tables update the way you expect