Release Management Template

Shepherd each release from planning and code freeze through RC and staging to production, with rollback ready.

Sign in with your Edesy account, then click Use template in the preview to create the board, with its sample cards, in your workspace.

Category

Product & Software DevelopmentRoadmapping & Feature Prioritization

Ideal for

Technology & Startups

Columns

Planned → Code freeze → Release candidate → Staging → Released

Sample cards

7

Custom fields

RICE score, Release

Request form

Creates cards in Planned

Columns and sample cards

The 5 columns of this board with its 7 sample cards, labels and fields, as they open in Edesy Boards. Copy the template to move cards and edit it.

  1. Planned

    2
    • v4.0 – scope and datesPriority: highMajor
      Release:
      4.0
    • v3.9 code freeze FridayPriority: mediumMinor
      Release:
      3.9
      Checklist 0/5: Problem, Spec, Design, Build, Launch
  2. Code freeze

    1
    • Cut RC1 and run regression suiteMinor
      RICE score:
      8
      Checklist 0/4: Tag build, Regression, Performance check, Sign-off
  3. Release candidate

    2
    • Write release notes for 3.9Priority: lowRelease notes
      RICE score:
      3
    • Rollback plan for database migrationPriority: highRollback plan
      RICE score:
      13
      Checklist 2/3: Interview customers, Size opportunity, Prioritise
  4. Staging

    1
    • Hotfix 3.8.2 – login timeoutPriority: urgentHotfix
      RICE score:
      1
  5. Released

    1 · done stage
    • v3.8 releasedMinor
      Release:
      3.8

Labels

Major, Minor, Hotfix, Release notes, Rollback plan

Custom fields

RICE score (Number, on card), Release (Text, on card)

Request form: Feature request · Release Management

Tell us what you need; it lands on the “Planned” column of this board. Asks for Title, Description, Priority, Attachments; each submission becomes a card in Planned.

Card templates

Feature

Release Management Template: questions

Yes, through the board request form. Share its public link; each submission becomes a card in the chosen column, with the answers in the card fields. Viewers of a shared read-only board link can see the board without an account.

Yes. Board automations run when a card is created, moved, assigned, labelled, completed, due soon or overdue, when a form is submitted or on a schedule, and can move, assign, label or archive the card, add a checklist or comment, create another card, call a webhook or post to Slack.

Related templates