Deployment history, developer-raised story pull requests and steadier sprint planning

Delivery

A deployment history on your Release Board

• A History tab shows every recorded deployment per environment
• Recording a deployment suggests the next version, based on the last one recorded
• The history loads faster and refreshes straight after you record a deployment

Developer workflow

Developers can raise story pull requests

Raising the pull request for a story is no longer limited to delivery managers and architects.

• The developer role can now raise a story pull request
• If an open pull request already covers the same branches, Konductro links to it instead of failing
• In multi-repository stories, the story branch is created on the task’s own repository from the base branch you selected

Planning

Reassign a technical analysis that is under way

• A technical analysis that has been picked up but not submitted can be moved to another team member from the phase workspace
• The option disappears once the analysis is submitted, and on completed or skipped stages

Sprint planning

Steadier sprint planning

• Story order holds across reloads, and adding or removing stories behaves correctly
• Tasks whose story is not yet approved are hidden from the sprint backlog instead of failing silently when added
• If a task cannot be added, you see why

Testing

QA results where you expect them

• QA outcomes show in both the story overview and the Testing tab, so they agree
• Starting a QA round assigns it to the person who started it
• Only the criterion you are working on shows its attachment panel

Quality of life

Smaller things that should feel better

• Search when linking an existing repository
• The Projects page opens filtered to active projects