Developers can shape stories, with a review step you control

Stories

Developers can change stories, and you decide how far

Until now only planning roles could create or edit a story, so a developer who spotted a wrong acceptance criterion had to find someone. Each project can now choose.

• Three settings under Settings, then General: planning roles only, developers with review, or developers without review
• Under review, a change applies straight away and then waits for an SDM to approve or reject it, so nobody is blocked
• Rejecting restores the previous title, description and acceptance criteria exactly, and the developer is told
• A story with an unresolved change does not move to Ready for QA. Resolving it either way releases it
• A Changes to review list shows what is waiting, field by field

Every existing project starts on planning roles only. Developer story access is something an SDM switches on.

Work items

Priority on stories and bugs

• Set critical, high, medium or low on a story or standalone bug, shown as a pill wherever it appears
• Filter by several priorities at once on the Work Items page
• Group the page by priority
• Everything starts unset, so your backlog is unchanged until you use it

From your AI coding tool

File and correct work without leaving your editor

• Create a story, task or bug. The project is worked out from the repository, so you are never asked which project you are in
• Correct the title, description or acceptance criteria on work you own
• Delete a task or bug that has not been started. Stories cannot be deleted this way, because deleting one takes its tasks with it
• Everything created lands in Draft and still needs an SDM’s approval
• A refusal says whether it was the project setting, your project role or your seat, and what to ask for

Update your Konductro plugin to use these commands.

Delivery

Release history you can search

• Pick an environment and see only what went to it
• Narrow to a period with presets, or set your own date range
• Sort and page through the results
• Your selection stays set when you come back
• Long release notes and story chips display properly

Also new

Other things worth knowing about

• Put stories and standalone bugs into a phase when you create them or afterwards; anything unplaced stays in Ad-hoc
• Developer notes on a story: a running record of decisions and gotchas, carried into each task’s context
• Backlog is renamed Work Items, and its header counts bugs separately from stories
• Every dropdown was rebuilt: correct in dark mode, usable from the keyboard and labelled for screen readers
• Stale pull requests on the Command Centre link through to a per-project breakdown, and the count is now correct
• Read-only members can add, edit and delete their own comments
• Story tabs are in the URL, so a link opens the tab you meant

Quality of life

Fixes, including one that blocked work

• Deleting or completing a sprint no longer leaves its tickets stuck in In Sprint with no sprint behind them. Tickets already in that state can be recovered
• The progress bar is correct for items in QA
• Standalone bugs reach Verified and can be recorded in a deployment
• QA permissions are enforced on completing a round, filing a bug and editing criteria
• Filters and selections stay set on Work Items and the sprint board
• Dark mode fixes for date pickers, scrollbars, secondary buttons and dialog options
• Planning conversations stop retrying when access is refused, and tell you why