Document version history, per-project webhooks and bulk backlog assignment

Documents

Every planning document keeps its full history

Requirements, technical analysis and phase architecture documents now keep every revision. Compare any two side by side and see whether you are reading the approved version or a working draft.

• Open the history from the document toolbar. Anyone who can view the document can see it, reviewers included
• Pick any two versions and see the differences highlighted in the rendered document
• One click compares the current draft with the last approved version
• The header shows whether you are on the approved version or a draft built on it
• Versions are captured as documents are generated, edited and approved; approval collapses drafts into one numbered version

Integrations

Webhooks per project, now with Bitbucket

Webhook setup now lives in each project. Generate a signing secret under Settings, then Webhooks, and point your git provider at Konductro so pull request status flows back securely.

• Each project has its own secret, shown once when it is generated, so rotating one never affects another
• Bitbucket Cloud pull request opened, merged and declined events now sync, alongside GitHub, Gitea and Azure DevOps
• Signatures are verified for GitHub, Gitea and Bitbucket; Azure DevOps uses Basic authentication

Developer tooling

Konductro now runs in Cursor

Cursor joins Claude Code, Amazon Q and OpenAI Codex as a supported AI coding tool. Pick up assigned work, load ticket context, start a branch and open a pull request without leaving Cursor.

• List your tickets, start work, decompose stories and open pull requests from Cursor
• Install the Konductro Cursor plugin from npm and run its setup
• Four AI coding tools supported: Claude Code, Amazon Q, OpenAI Codex and Cursor

Planning

Assign a whole batch from the backlog

• Select several backlog items and assign them to a team member in one action, useful when a decomposed story produces a stack of tasks
• Backlog filters stay set between visits

Team

Clearer, safer role management

The project roles offered for a team member now follow what their account can do, and changing a user’s role shows the effect before you confirm.

• The team editor only offers project roles the member can hold
• Changing a user’s role shows which of their project roles change, across every project, before you commit
• Each automatic adjustment is recorded in the audit log

Quality of life

Smaller things that should feel better

• A rare write conflict in planning conversations is fixed, and approvals reset correctly when a document is regenerated
• Stage cards update live
• Approve and reject controls are hidden while a stage waits for resubmission
• The Save button in the add team member dialog is always reachable