Comments, multi-approver workflows and story-level branching

Collaboration

Comments on every ticket and story

Tickets, tasks, stories and bugs now have a Comments tab. The discussion stays attached to the work, instead of happening in Teams or email.

• @-mention teammates. They get an in-app notification, a Teams message and an email that links back to the ticket
• Attach images, PDFs and documents. Images show as inline previews; click for full size
• Edit and delete your own comments. A deletion leaves a marker so the record stays intact
• Mention suggestions are limited to the project’s team

Planning

Multi-approver workflow on phase stages

Stage approvals are no longer single-approver. Assign several reviewers to Requirements, Technical Analysis and Phase Architecture, and set them up in advance, even on stages that are still locked.

• Blocking or advisory: only blocking approvers gate the stage, and advisory reviewers can be brought in for context
• Set reviewers once at the start of a phase; they show as pills under each stage
• The stage closes itself on the last approval, with no separate advance step
• When a developer submits a technical analysis from a Konductro plugin, pre-configured reviewers are notified automatically
• Every assignment, submission, approval, rejection and resubmission is recorded with the person’s role at the time
• Resubmitting after changes resets earlier approvals and notifies reviewers of the new version

Delivery

Choose your branching strategy per project

Some teams want one branch and pull request per task; others want one branch per story with a single pull request covering all its tasks. Each project can now choose.

• Branch per task: one branch and one pull request per task, as before
• Branch per story: the first task on a story creates a shared branch, later tasks reuse it, and Conductor opens one pull request for the whole story
• A progress panel on the story shows which tasks are done, in progress and still to start
• Conductor drafts the story pull request description from the story, its tasks and commits; you edit and confirm before it is raised
• The strategy is fixed on each ticket when work starts, so changing the project setting does not disturb work in progress

Quality of life

Smaller things that should feel better

• Admins can resend an invite to someone who has not logged in yet
• Sign-in details now come directly from the identity provider, with a separate welcome email
• Viewers can no longer trigger changes by accident, and the audit log records the role of whoever acted
• Reassigning a decomposition task flags team members who have no CLI token before you pick them
• Mention notifications for bugs open the right view
• Several test round fixes