Solutions · Release Management

Know exactly what shipped, and when

Versioned releases, deployment status and an archive of shipped work make every release easy to trace.

Who it's for

Teams that need a clear record of what shipped, when, and in which version.

  • Versioned releases with notes and dates
  • Planned, Deployed, Rolled Back and Archived states
  • Work items linked to their release
  • Shipped Kanban tasks kept in the archive
Releases · Customer portalv2.4.0 deployed
v2.4.0Self-service password resetDeployedOct 02
v2.4.1Hotfix: invoice roundingPlannedOct 12
v2.3.2Payment gateway switchRolled backSep 18

How it works in Taskmei

  1. Plan the release

    Create a versioned release with a planned date and notes.

  2. Link the work

    Associate backlog items with the release they ship in.

  3. Record the outcome

    Mark releases as Deployed or Rolled Back so history stays accurate.

  4. Keep shipped work

    Archived Kanban work and closed sprints stay searchable with their reports.

Can a release be rolled back?

Yes. Mark it as Rolled Back so the history shows exactly what happened.

Where does shipped Kanban work go?

Archive done cards from the board; they move to the archive with the project, board and ship date.

Can we see releases per project?

Yes. The release register lists releases for each project with version, status, dates and notes.

Run your next sprint in Taskmei

Free plan for small teams. Scrum, Kanban and Hybrid boards, AI-drafted backlogs and live delivery dashboards.