Review the task plan, then move work forward
Inspect task dependencies, correct potential conflicts, and send selected tasks to Jira with a result for each task. Activate tested imports for daily or weekly runs, apply initiative proposals individually, and record confidence alongside Key Result progress.
What changed
- Explore task dependencies in a movable Work map and review potential conflicts
- Activate a tested import on demand, daily, or weekly, with pause and resume controls
- Apply an initiative decision proposal individually, including its pending prerequisites
- Record confidence and blockers in Objective check-ins, alongside the numbers
Inspect and correct the plan before handoff
Task plan brings Tasks, Work map, and Potential conflicts together. Move map nodes, follow the prerequisite paths into a selected task, and open its details without losing your place on the map. Review suggested title and description changes for potential conflicts, with controls to apply or restore them. Send selected tasks to Jira, see which succeeded, and retry only the failures.
Start recurring imports from a tested setup
Eligible workspace admins can activate a tested saved import with On demand, Daily, or Weekly. Connecting a source alone does not start imports. Pause and resume from the import, and keep the selected policy if a plan or usage limit prevents a run. Scheduled imports are now available on Team; exact run times remain managed by Zentrik.
Apply a proposal and keep proof of shipment
Each pending initiative decision proposal has its own Apply action. It also applies pending prerequisites and leaves unrelated selections intact. In GitHub settings, owners and admins can specify each repository’s production branch. An active closing reference can then mark its Idea as shipped when merged work reaches that branch. The Idea keeps its latest shipment receipt, including after reopening; related links alone do not mark it as shipped.
Record the judgment behind Key Result progress
Objective check-ins now capture whether the team expects to hit each Key Result and what is blocking it. Each confidence call keeps its reason and author, shows the change from the previous call, and preserves earlier calls. The check-in focuses on Key Results that need attention, with measurement details available when needed.
More in this release
Planning and Discovery
- Draft a delivery role’s name, responsibilities, and task settings from a short description, then edit the draft before creating it
- Change Insight, Opportunity, and Idea status directly from their table rows when you have edit access
- Find consistent row commands in visible menus and right-click menus across more planning and Discovery tables
- Initiative next steps and decision-analysis dependency references are more reliable
- Discovery panels fit narrow screens more reliably, and new Huddle widgets receive focus when opened
- Task details put the description first, and the task table supports numeric Points sorting
- Team members hides the Default view column when no saved filters are available
Imports, conversations, and search
- Edited analytics questions keep new results linked to their Insight; previous results retain their original question context
- Saved imports show a retry action when loading fails instead of appearing empty
- Slack retries can recover messages after a queue failure; imported thread context preserves mentions and line breaks more faithfully
- Search public docs, articles, releases, or all content, with direct links to matching sections and filters preserved when you go back