Release notes

What has shipped in Konductro, newest first. Smaller fix-only releases are not listed.

2610.03·14/10/2026

My Work, rebuilt around what needs you

My Work shows everything assigned to you, grouped by status and project, including work that is not in a sprint
Pull requests waiting for your review, and an SDM’s approvals and story changes, sit on the same page
A navigation badge counts what needs you, in red when something is blocked
Finished work held for a QA or UAT deployment says so, instead of looking stuck
Faster sprint planning, and an active sprint card that shows the days left

2610.01·01/10/2026

Set the sections of your requirements, technical analysis and phase architecture documents for the workspace, or per project
Every document records the template that produced it, and a template in use cannot be changed
What you can do inside a project now depends on your role on that project’s team, not your account type
Email notifications can arrive immediately or as an hourly or daily digest
Optionally hold stories out of QA or UAT until a deployment to that environment is recorded

2608.02·24/08/2026

Each project chooses whether developers may create and edit stories, and whether an SDM reviews the change
Rejecting a reviewed change restores the story exactly as it was
Priority on stories and standalone bugs, with filtering and grouping on Work Items
Create, correct and delete work items from your AI coding tool. Anything created still starts in Draft
Release history filters by environment and date range

2608.01·05/08/2026

Every developer brief keeps its history, and any earlier version can be restored
Bugs appear on the delivery board, the release board and in deployments, like the rest of your work
Move a whole selection into the active sprint in one action, stories together with their tasks
Phases get your own categories and a priority, with filtering and grouping

2607.02·15/07/2026

Set a story or task’s status directly, with a required reason kept in its history
Archive finished stories together with their tasks, and restore them in a click
Group and filter the testing board by phase, search stories and reassign testers from the board
Rename and delete sprints, with guards so active work is not lost
A filterable activity log for each project

2607.01·08/07/2026

Every bug and feature request gets a permanent reference, included in your confirmation
Each item has its own discussion thread for questions and replies
Bug reports stay private to your workspace, while feature requests are shared for everyone to vote on
New teams can create a workspace and start a trial themselves

2606.06·25/06/2026

The Release Board keeps a history of every deployment per environment and suggests the next version
Developers can raise the pull request for a story themselves
A technical analysis that is under way can be reassigned to another team member
Sprint planning keeps story order and no longer offers tasks it cannot add

2606.04·09/06/2026

Planning documents keep every version, with a side-by-side comparison against the last approved one
Webhooks are set up per project with their own signing secret, and Bitbucket Cloud joins GitHub, Gitea and Azure DevOps
Konductro now works in Cursor, alongside Claude Code, Amazon Q and OpenAI Codex
Select several backlog items and assign them in one action
Changing a user’s role shows the effect on their project roles before you confirm

2606.01·01/06/2026

Choose, per event, whether you are told in-app, in Microsoft Teams, by email or not at all
Describe a bug in your own words and Conductor drafts a structured ticket for you to review
Developers can refine an assigned bug from their AI coding tool through the Konductro plugin
The backlog shows only work not yet started by default, with toggles for in progress, done and archived

2605.07·21/05/2026

Comments on every ticket, task, story and bug, with @-mentions and file attachments
Multiple reviewers on Requirements, Technical Analysis and Phase Architecture, each set as blocking or advisory
A stage closes itself on the last approval, and every step is recorded in the audit log
Choose per project between a branch per task or one shared branch and pull request per story

Before May 2026

Numbered release notes begin with 2605.07. By then, Konductro already covered the delivery loop from planning to QA:

Planning with Conductor in three stages, requirements, technical analysis and phase architecture, each reviewed and approved
Technical analysis, story decomposition and ticket work from Claude Code and Amazon Q through the Konductro plugins
Stories broken into tasks, with sprints and delivery boards for Scrum, Kanban and Konductro’s own methodology
Branches and pull requests on Azure DevOps, GitHub, Bitbucket Cloud or a Konductro-managed repository, with reviewers assigned automatically
Story-level QA with tester assignment, bugs filed against failed criteria, and a test library
Notifications in-app, in Microsoft Teams and by email