Decision partner chat, multi-product Jira imports, and a faster Discovery overview.
Ask workspace chat to prioritize and it now reasons across your ideas — RICE-ranked, with structured evidence and decision context. A Jira import can map each item to its own product from a field like Components, so one run spans your whole portfolio. The Discovery overview loads with only what it needs on first paint, products load leaner, and several interactions that needed extra effort now work the first time.
What changed
- Ask chat to prioritize and get RICE-ranked ideas with structured evidence and decision context
- Jira imports can map each item to its own Zentrik product from Components or any chosen field
- Discovery overview first paint loads only critical data; everything else defers until it is needed
- After a Jira import, a panel shows what was created — counts and links to signals, insights, or ideas
- Products load a lean payload; edits save immediately and the sheet closes cleanly
- Discovery sidebar closes with one click; initiative workspace header holds steady during load
Chat answers build prioritization questions
Ask the workspace assistant to help prioritize and it builds a decision slate — RICE-ranked top ideas drawn from your taxonomy, with evidence from signals and votes, readiness context, and recent decision activity. Answers use entity badges so you can click straight to any idea, account, or insight mentioned.
- Get a prioritized shortlist with evidence behind each idea
- See which ideas have the most demand and which are ready to commit
- Click any idea, account, or insight in the answer to open it
One import, multiple products
Jira imports can now map each item to its own Zentrik product based on a field you choose — Components is the common case for engineering backlogs. Items with a match land in the right product; everything else falls back to the selected default. You can also let Zentrik create any product it does not find, de-duplicated up front so concurrent imports do not race.
- One Jira query spans your whole product portfolio, not one query per product
- Components or any other field drives the product assignment per item
- New products are created once up front, not raced per item
Import closes with a summary, not a toast
After a Jira import finishes, a dismissible panel shows what Zentrik did with the data — how many signals, insights, and ideas were created, and direct links to each. Running and failed imports stay visible until you are ready to move on.
- See exactly what came in without navigating away to check
- Links go straight to the created signals, insights, or ideas
- Failed imports stay visible so you know what to retry
More in this release
Jira and integrations
Multi-product imports, better field handling, and a complete import flow.
- Components (or any field) maps each item to its own Zentrik product; missing products created once, de-duplicated
- Completion panel stays open after import with counts and links to what was created
- Reporter and Assignee always mappable; signal field suggestions favor customer evidence
- Expired connection prompts to reconnect; legacy OAuth scope checks corrected
- Signal list: quick filters for Jira-sourced signals and signals without insights
- Import dialog sizing refined
Discovery, products, and the app
Faster loads, cleaner interactions, and the decision partner.
- Decision partner: RICE-ranked ideas with evidence, readiness context, and decision activity
- Discovery overview: only the control-panel query on first paint; taxonomy and other reads deferred
- Products portfolio: lean endpoint, ~3x smaller payload
- Database query timeouts bounded — web requests fail fast instead of hanging
- Product edits save immediately; sheet close clears pointer-events locks
- Discovery sidebar close race fixed — one click now closes a restored sidebar
- Initiative workspace header holds steady during load
- User story priority settings: compact aligned layout