Product knowledge and Discovery evidence are easier to review.
This release gives teams a more deliberate way to bring source-backed product knowledge into Zentrik, then review what changed before it shapes future work. It also improves the workspace launchpad, Discovery source review, Jira idea imports, and connected-tool selectors so product context is easier to inspect and route across the systems teams already use.
What changed
- Source-backed product knowledge can be reviewed, edited, and applied with clearer evidence
- Workspace home now surfaces Discovery signals and product context entry points more clearly
- Discovery imports and evidence review are stronger across Jira fields, signal sources, transcripts, and linked records
- Jira, Linear, Aha, and backlog import and export selectors are easier to search
Product knowledge gets a review loop
Teams can bring product knowledge into Zentrik with source evidence, review proposed changes, edit the proposal, understand conflicts, and apply accepted updates. The goal is to make product context feel inspectable and governed instead of silently accumulated.
- Product knowledge updates can be checked against their sources before they shape AI work
- Conflicting context is easier to spot and resolve
- Teams can refine proposed updates before applying them to the workspace
Workspace home points to the right product work
The workspace launchpad now does more to surface Discovery signals and product context entry points. Opening a workspace should give teams a clearer read on where evidence, context, and next actions are waiting.
- Teams can move into Discovery review with less navigation overhead
- Product context is easier to find from the first workspace screen
- The launchpad better reflects the work happening inside the workspace
Discovery evidence review is more usable
Discovery gained Jira score-field mapping for idea imports, clearer signal and transcript source presentation, better retry feedback when linked evidence is still loading, and fixes for trend totals and opportunity tree relation counts.
- Imported Jira ideas can carry effort and impact context into review
- Source evidence is easier to inspect from Discovery records
- Reviewers get clearer feedback when related evidence is not ready yet
- Trend windows and relationship counts are more trustworthy during review
Connected-tool workflows are easier to search
Selectors across Jira, Linear, Aha, and backlog import and export flows now behave more consistently for searchable lists. That matters when teams have enough projects, fields, or destinations that scrolling through a static menu becomes slow.
- Setup and import flows are faster in larger connected-tool workspaces
- Teams can find the right project, field, or destination with less trial and error
- Backlog handoffs are easier to configure without losing product context
More in this release
Product knowledge and Discovery
User-facing improvements for product context, source evidence, imports, and Discovery review.
- Source-backed product knowledge intake with review, proposal editing, conflict handling, source evidence, and apply flows
- Workspace home launchpad polish with richer Discovery signals and product context entry points
- Jira score field mapping for Discovery idea imports, including effort and impact mapping controls
- Improved signal source viewing and transcript source presentation across Discovery records
- Clearer retry feedback when linked insight signals are still loading or unavailable
- Trend summary window totals fixed for Discovery reporting
- Opportunity tree relation counts fixed
Connected tools and reliability
Smaller fixes for connected-source workflows, examples, and platform steadiness.
- Searchable selectors improved across Jira, Linear, Aha, and backlog import and export workflows
- Gong transcript source formatting fixed
- Pendo NPS rating copy aligned in signal examples