Journal · August 2026
August 2026: fixes, Jira status sync and a wiki in Crew
- Covers:
- Last updated:
- Releases:
- 19
- Versions:
- 5.218.0 → 5.229.3
- Release days:
- 9
August was the quietest month, with 19 releases from 12 August on. Most of them fixed what daily use had shown: notifications, Jira statuses and task keys. One new feature stood out, a read-only Outline wiki inside projects and clients.
What shipped
- v5.218.0 (AVFORGE-353): a person is notified when a task is assigned to them, on every create and update path, not on two of eight.
- v5.223.0 and v5.224.0: the orchestrator delegates to its agents again, and deploy credentials reach the deployment agent, so an autonomous run reached production.
- v5.225.0: a status-only Jira sync mode for projects where Crew is the master but statuses still follow Jira.
- v5.226.0: task keys and Jira keys can no longer drift apart in projects where Jira owns the numbering.
- v5.227.0 (AVFORGE-360): a Wiki tab on projects and clients shows the matching Outline pages inside Crew.
- v5.228.0: status changes made in Crew no longer revert on the next Jira sync.
- v5.229.0 (AVFORGE-369): plan, description and designs can be read back through the v1 task API, not only written.
Features
Jira sync, API and MCP
Jira projects can be imported once or kept in two-way sync, so a team can move over step by step. A documented v1 API and an MCP server let tools and Claude work with Crew.
Crew as a Jira alternativeAI agents and run gates
Agent teams write code, test it, open pull requests and deploy in isolated containers. Crew Runs stop at gates where a person approves before anything is released.
October 2026 chapter