Week of July 27, 2026
Themes can now produce Work Items and Changes directly, with a one-click export to GitHub or Jira and a dedicated Work Items layer in the Delivery Graph. Merged pull requests close the matching issue on both sides. Incoming emails keep their raw text and arrive with AI-cut evidence chunks. Highlight: strategy hands off to delivery without leaving Outcomet.
In this edition
From a theme to a ticket in one step
The gap between deciding something and someone picking it up has been the manual part of the loop. Not anymore. Work Items and Changes can be created directly from a Theme, and optionally exported to GitHub or Jira with one click, so the handoff to engineering happens where the decision was made rather than in a separate tab twenty minutes later.
Read moreRead less
The Delivery Graph shows the result. Work Items render as their own layer sitting above Themes, so you can see which tasks belong to which strategic initiative and, more usefully, which themes have nothing under them at all.
Tracking then keeps itself honest. When a linked pull request is merged or closed, the corresponding GitHub issue closes on GitHub and in the workspace, so the two stop drifting apart the way they always do when someone has to remember.
- Create Work Items and Changes directly from a Theme
- Optional one-click export of a Work Item to GitHub or Jira
- Work Items rendered as a dedicated layer above Themes in the Delivery Graph
- Merged or closed pull requests close the matching GitHub issue on GitHub and in the workspace
Agents can run the work items
The MCP Agent can now fully manage Work Items: create, update, delete, search, and link or unlink them. A connected agent can maintain the task layer on your behalf, which is the point where automation stops being a read-only observer of your workspace and starts doing the bookkeeping.
Read moreRead less
- MCP Agent support for creating, updating, deleting, and searching Work Items
- Linking and unlinking Work Items through the agent
Emails arrive with the evidence already cut
Email feedback now keeps the full raw text of the original message, so there's a verifiable source behind whatever gets extracted from it. On top of that, incoming emails automatically generate AI-assisted evidence sub-chunks, short review-ready highlights, so a long mail turns into triageable pieces before anyone opens it.
Read moreRead less
- Full raw email text preserved for every email feedback submission
- Automatic AI-assisted evidence sub-chunks generated from incoming emails
Drawers keep their controls
Detail drawers hold onto their close and resize controls while you scroll, keep the alignment you configured, and retain their styled background instead of going flat halfway down. Small things, all of them the kind you notice only when they're broken.
Read moreRead less
- Detail drawers keep close and resize controls, alignment, and styled backgrounds while scrolling
- Page style copy and reset now include Signals settings, so signal configurations survive a style copy
- Legacy browser preferences load safely for consistent appearance on older browsers
What this means for you this week
- Turn a theme into a tracked work item and push it to GitHub or Jira without leaving the decision.
- See tasks positioned against the initiatives they belong to in the Delivery Graph.
- Stop closing the same issue twice, once in the repo and once in the workspace.
- Let a connected agent maintain the work item layer for you.
- Triage a long email from its extracted highlights, with the original still attached as evidence.
If you want a walkthrough of creating work items from themes, the GitHub and Jira export, or the new email evidence chunking, reply here and I'll set up a quick demo.