Sealstep
Data Center → Cloud · free template packs

Checklist template packs for your Jira Cloud move

Moving from Jira Data Center to Cloud means rebuilding the process checklists that lived in old apps, wiki pages or people’s heads. Here are four starting points: Definition of Done, QA sign-off, release readiness and onboarding. Copy them as markdown and adapt them to your team.

Free to use in any tool. In Sealstep they’re built in as starter packs, with required items pre-marked. The markdown uses the widely used Smart Checklist syntax (-! = required, # = section), so it pastes into Sealstep and other apps that read that format.

Data Center end of life: Atlassian has announced that Data Center products reach end of life on March 28, 2029 (Atlassian blog). Rebuilding checklists is a small but easy-to-forget part of the move.

Definition of Done (software)

A team-level Definition of Done for stories and tasks.

  1. Build
  2. Acceptance criteria met and demoed to the requesterRequired
  3. Code reviewed and approved by at least one teammateRequired
  4. Automated tests added or updated, and passing in CIRequired
  5. No new linter or static-analysis warnings
  6. Ship
  7. Merged to the main branchRequired
  8. Feature flag or rollout plan noted on the issue
  9. User-facing docs or release notes updated
  10. Product owner accepted the work

Markdown 

## Build
-! Acceptance criteria met and demoed to the requester
-! Code reviewed and approved by at least one teammate
-! Automated tests added or updated, and passing in CI
- No new linter or static-analysis warnings
## Ship
-! Merged to the main branch
- Feature flag or rollout plan noted on the issue
- User-facing docs or release notes updated
- Product owner accepted the work

QA sign-off

Verification steps before a ticket moves to Done or Ready for release.

  1. Test
  2. Test cases written or linkedRequired
  3. Happy path verified on stagingRequired
  4. Edge cases and error states verifiedRequired
  5. Tested on supported browsers / devices
  6. Accessibility smoke check (keyboard + screen reader labels)
  7. Close out
  8. Regression suite greenRequired
  9. Bugs found are linked as separate issues
  10. QA owner signed off
    Assign this item to the QA owner and set it Done when signing off.    Required

Markdown 

## Test
-! Test cases written or linked
-! Happy path verified on staging
-! Edge cases and error states verified
- Tested on supported browsers / devices
- Accessibility smoke check (keyboard + screen reader labels)
## Close out
-! Regression suite green
- Bugs found are linked as separate issues
-! QA owner signed off
> Assign this item to the QA owner and set it Done when signing off.

Release readiness

Run on the release ticket before tagging and deploying.

  1. Before
  2. All issues in the fix version are resolvedRequired
  3. Release notes draftedRequired
  4. Rollback plan documentedRequired
  5. Stakeholders notified of the release window
  6. Deploy
  7. Build tagged and artifacts publishedRequired
  8. Deployed to productionRequired
  9. Post-deploy smoke test passedRequired
  10. After
  11. Monitoring and error rates checked after 1 hour
  12. Fix version marked released in Jira

Markdown 

## Before
-! All issues in the fix version are resolved
-! Release notes drafted
-! Rollback plan documented
- Stakeholders notified of the release window
## Deploy
-! Build tagged and artifacts published
-! Deployed to production
-! Post-deploy smoke test passed
## After
- Monitoring and error rates checked after 1 hour
- Fix version marked released in Jira

Employee onboarding

IT and team tasks for a new starter. Use one issue per person.

  1. Before day 1
  2. Laptop ordered and set upRequired
  3. Accounts created (email, SSO, chat, Jira)Required
  4. Buddy assigned
  5. Week 1
  6. Welcome meeting heldRequired
  7. Team rituals and calendars shared
  8. First starter ticket assigned
  9. Day 30
  10. 30-day check-in completed

Markdown 

## Before day 1
-! Laptop ordered and set up
-! Accounts created (email, SSO, chat, Jira)
- Buddy assigned
## Week 1
-! Welcome meeting held
- Team rituals and calendars shared
- First starter ticket assigned
## Day 30
- 30-day check-in completed

How to use these in Sealstep

  1. As a Jira admin, open Jira settings → Apps → Sealstep Checklists → Templates. On a new site the four packs are offered as one-click starters.
  2. Edit the items to match how your team works. Keep required items few and meaningful: each one can block a transition.
  3. Choose where it applies (all projects or selected ones), turn on Auto-apply on create for the right issue types, and lock it if it encodes policy.
  4. Add the Sealstep validator to the transitions that should respect it.

Writing a good Definition of Done

  • Make it checkable. “Code reviewed by a teammate” beats “Quality is good”.
  • Separate DoD from acceptance criteria. DoD applies to every item. Acceptance criteria are specific to one story. Put those as items on the story itself.
  • Use N/A deliberately. If a step often doesn’t apply, mark it N/A with a short detail note. Don’t delete it.
  • Review it every quarter. Edit the template. Issues already created keep the version they started with.