SealstepUsing Sealstep
Everything in one page: the issue panel, templates, the workflow gate, JQL, history and admin settings.
The checklist panel
Open any issue and click Checklist in the issue’s apps area. Type an item and press Enter. Start a line with # for a section header or ! for a required item. Paste several lines (bullets, Smart Checklist markdown, or - [ ] task lists) to add them all at once.
- Statuses: To do, In progress, Done, Skipped, N/A. Click the checkbox to toggle Done, or the status label for the others. Done and N/A count toward progress.
- Per-item: assignee, due date, details (multi-line notes), required flag. Use the ⋯ menu.
- Formatting:
**bold**,*italic*,`code`,~~strike~~,[links](https://…), bare URLs, and issue keys like DEV-42, which become links. HTML is never rendered. - Reorder: drag the handle, use Alt+↑/↓, or use Move up/down in the ⋯ menu.
- Delete shows an Undo toast. Undo restores the item in place.
- Hide completed (eye icon) declutters long lists.
- Export: ⋯ → CSV, markdown, or history CSV.
Keyboard shortcuts
| ↑/↓ or k/j | Move between items |
| Space or x | Toggle done |
| 1–5 | To do, In progress, Done, Skipped, N/A |
| Enter or e | Edit text |
| r | Toggle required |
| Alt+↑/↓ | Move item |
| Delete | Delete (with undo) |
| n | Add a new item |
| ? | Show shortcuts |
Templates & auto-apply
Admins manage templates in Jira settings → Apps → Sealstep Checklists → Templates. A template can be global or limited to selected projects. With Auto-apply on create, it is added when a new issue matches its issue types and, optionally, labels. Anyone who can edit a checklist can also apply a template from the panel’s Templates menu. A template is applied once per issue.
Locked templates: items from a locked template can be ticked, assigned and dated by anyone with access. Only Jira or project admins can rename them, make them optional or delete them.
Workflow validator (DoD gate)
- Open your workflow in the workflow editor and select the transition (for example → Done).
- Add the validator Sealstep – required checklist items finished and publish the workflow.
- Test it: on an issue with an open required item, the transition fails with a message like “1 required checklist item is not finished: ‘QA sign-off’. Mark it Done or N/A in the Sealstep checklist, then try again.”
Settings: Skipped counts as finished (off by default), and what happens if Sealstep can’t read a checklist: pause the transition (default) or let it through. Issues without a checklist always pass. The validator runs in company-managed projects and, where Jira supports app validators, team-managed projects.
JQL fields
| Field | Type | Example |
|---|---|---|
checklistProgress | number 0–100 | checklistProgress < 100 |
checklistRequiredOpen | number | status = Done AND checklistRequiredOpen > 0 |
checklistOpen | number | checklistOpen = 0 |
checklistTotal | number | checklistTotal > 0 |
checklistComplete | "true"/"false" | checklistComplete = "true" |
checklistAssignee | user | checklistAssignee = currentUser() |
checklistNextDue | date | checklistNextDue <= 7d |
checklistUpdated | date | checklistUpdated >= -1d |
Jira indexes these from the sealstep-checklist issue property that Sealstep updates on every change.
Sealed history
Every change (add, edit, status, assignee, due date, reorder, delete, template, import) is appended as an event with the actor, time, a summary and a SHA-256 hash covering the event and the previous hash. Events are written with “fail if exists” keys, so they’re never overwritten. The latest seal is also stored on the Jira issue. Verify history recomputes every hash and compares the head with both anchors. That detects edited, deleted, reordered or truncated events. Export as CSV from the History view or the ⋯ menu.
Sealed history is process evidence. It does not make tampering impossible, and it isn’t legal or compliance advice.
Importing
Per issue: Import in the panel accepts Smart Checklist markdown, generic markdown lists, CSV (columns such as Text, Status, Required, Assignee, Due, Details) or plain lines. It shows a dry-run preview first. In bulk: admins use Migrate from Smart Checklist. See the migration guide.
Admin settings & permissions
- Who can tick, assign and set due dates: people who can edit the issue (default), people who can transition it, or anyone who can see it.
- Who can add, rename, reorder and delete: people who can edit the issue (default), or project admins only.
- Defaults: new items required by default; pause all auto-apply.
- Data export: all checklists (CSV), templates (JSON); template import.
Licensing
Paid tiers are sold and billed through the Atlassian Marketplace. If a site’s subscription is inactive, checklists remain visible but read-only, templates don’t auto-apply, the validator lets transitions through, and nothing is deleted.
Limits
Up to 500 items per checklist, 1,000 characters per item, 4,000 characters of details, 200 templates of up to 300 items each.