Source Health and Cleaner Output
This week was about making Humm easier to trust while you work. Integrations became much clearer about what needs attention, and markdown-heavy answers render more cleanly across threads and reports.
Integration Health Is Easier to See
If a source needs to be re-authenticated, Humm now tells you directly with a banner instead of leaving you to infer it from missing data. The integrations sources list also shows per-source status badges like Healthy, Auth Failed, Disconnected, Syncing, and Disabled, so you can tell what is broken and what is just in progress at a glance.
Jira Product Discovery Is Now a First-Class Connector
Humm now includes a dedicated Jira Product Discovery connector, which lets you pull JPD insights into the system with a connector designed for that product instead of treating it as a Jira edge case. In practice, that means cleaner setup, more reliable project resolution, and a better path for analyzing product feedback and insight snippets tied to JPD projects.
Markdown, Math, and Reports Render More Cleanly
We migrated markdown rendering onto a new pipeline that does a better job with richer answer content, including math, structured formatting, and report details. This is the kind of change you mostly notice because things stop looking fragile: fewer formatting oddities, cleaner report run details, and more consistent rendering across thread content.
Improvements
- Polished spacing and alignment on the integrations sources page so the list reads more cleanly.
Bug Fixes
- Fixed Jira Product Discovery OAuth routing issues that could block the connector from working reliably.
- Fixed the organization switcher so keyboard focus no longer gets trapped after an org change.
- Fixed Jira Product Discovery site resolution in production.