Ideas push back to Jira, and the interface gets a cleaner, more accessible pass.
Jira sync now goes both ways: you can push a Zentrik idea back to its linked Jira issue. A design-system and accessibility pass makes focus, dividers, and overlays consistent and brings every control within reach of the keyboard and screen readers. Idea scoring also reasons about your existing product, not an idea's text alone.
What changed
- Push a Zentrik idea back to its linked Jira issue — the summary by default, with description and status opt-in
- Idea scoring reasons about your existing product — feature map, personas, KPIs, and mission — instead of treating shipped capabilities as new
- A design-system pass makes focus rings, dividers, and overlays consistent across the app
- Every control is reachable by keyboard and screen reader: icon-only buttons carry names, and focus rings show only for keyboard users
- Curated idea status survives an integration re-import instead of being overwritten
- Imported PDFs and Word documents extract reliably, where some previously came in as garbled text
Jira sync starts going both ways
Until now the Jira integration only imported. You can now push a Zentrik idea back to its linked Jira issue. The summary goes by default; description and status are opt-in. Status changes use Jira's own workflow transitions, so a status with no available transition is reported rather than forced. Nothing syncs automatically — each push is deliberate.
- Decisions made in Zentrik reach the issue your engineers work from
- You choose what travels: summary, description, status, or just one
- Status respects the Jira workflow instead of writing an invalid value
Idea scoring understands your product
When Zentrik evaluates an idea, it now reads a structured packet of your product — the feature map, personas, KPIs, tech stack, and mission — rather than the idea's text alone. Scoring reasons about the product boundary you already have, so an idea that overlaps a shipped capability is recognized instead of treated as brand new. Document import also got more reliable, so the knowledge behind that reasoning is cleaner.
- Effort and impact estimates account for what you have already built
- Ideas that overlap existing features are recognized, not double-counted
- Imported documents land as readable text, not garbled extraction
A cleaner, more accessible interface
A staged design-system pass unified the pieces that drift over time: a named overlay layer, consistent dividers, and a single calm focus ring. Focus rings now appear for keyboard users and stay out of the mouse's way. Icon-only buttons carry accessible names, and dozens of surfaces that were silently transparent now render at the intended opacity.
- The interface reads consistently instead of subtly different per surface
- Keyboard and screen-reader users can reach and identify every control
- Menus and flyouts render solid instead of see-through
More in this release
Integrations and Discovery
Two-way Jira sync, product-knowledge grounding, and import reliability.
- Push a Zentrik idea to its linked Jira issue — summary by default, description and status opt-in
- Idea evaluation reads a product-knowledge packet: feature map, personas, KPIs, and mission
- PDFs, Word documents, HTML, and Markdown extract with structure
- Jira import shows which fields it cannot bring across, and supports people-picker fields
- Curated idea status preserved on integration re-import
- Opportunity tree honors the active scope when opened directly
Interface and accessibility
A pass to make the interface consistent and reachable.
- One consistent focus ring, visible only for keyboard users
- Icon-only buttons carry accessible names
- Menus and flyouts render solid instead of see-through
- Collection, Products, and Roadmap headers aligned with the rest of the app