Stanki Guild

Jira app

Checklist Flow for Jira: definition of Done checklists your Jira workflow enforces

Mark the items that matter as Required, and Jira will not let the work item move on until they are done.

View on the Atlassian Marketplace

Who it is for

#
  • Engineering, QA and release teams that keep a Definition of Done or Definition of Ready in people's heads or in a wiki.
  • Jira administrators who want the workflow, not a reminder, to stop a work item that is not finished.
  • Teams that need a record of who checked what and when, for their own audits.

What it does

#
  • Required items block the transition. A workflow validator stops the transition until every Required item is checked or marked not applicable. The message names the items still open.
  • Several named checklists on one work item. Keep a Definition of Ready and a Definition of Done side by side, each with its own progress and its own validator setting. Free in every edition.
  • Templates. Start each work item with the right items, by hand or, with a paid licence, on the Create dialog or automatically by work type. The app ships 49 ready-made checklists; five are free in every edition and the rest need a paid licence.
  • A history that cannot be cleared in the app. Every change is written to a hash-chained history that no role can clear, and you can export it as CSV, JSON or a PDF.
  • Find unfinished work with JQL. 13 JQL fields and a read-only Checklist progress field show which work items have an open Definition of Done. A My checklist items dashboard gadget lists the open items assigned to you.
  • Roles and permissions. Decide who may check items, edit a checklist, make a Required item weaker, manage templates and settings, with a log of every change. Groups, project roles and named people need a paid licence.
  • Turn an item into a work item. Create a sub-task or a linked work item from a checklist item, as you, and tick the item automatically when that work item is done. A newly assigned person gets an e-mail.
  • Workflow post function (paid). Check or uncheck every item, clear item statuses or apply a template when a work item moves through a transition.
  • Jira Automation actions (paid). Apply a template, add an item, tick an item or read the status from your own Automation rules, so Slack, Teams or e-mail alerts stay in your Jira.
  • Release readiness (paid). A go / no-go view per fix version with a PDF record, counting only Approval Flow approvals that are verified.

Every feature is described in the documentation. Features marked paid need a paid licence; sites with up to 10 users get every feature free.

How it works

#
  1. Put a checklist on a work item, or start from a template, and mark the items that must be done as Required.
  2. A Jira administrator adds the validator Checklist Definition of Done to the workflow transitions that should be gated.
  3. People tick items in the work item panel. Jira blocks the transition until the Required items are done, and the history records every change.

Product video

#

A short product video will be shown here. It is not recorded for the website yet.

Pricing and installation

#

Install it from the Atlassian Marketplace listing (Checklist Flow: Definition of Done for Jira). Billing, trials and licences are handled by Atlassian.

Free, with every feature, for sites with up to 10 users. Prices above that are on the pricing page and on the Marketplace listing.

Security and your data

#

Checklist Flow for Jira is an Atlassian Forge app. It has no Forge remote, no web trigger and no calls to external hosts. Its records are kept in Forge hosted storage on your own Atlassian site and follow Atlassian's data-residency arrangements for that site. We run no servers for the apps and use no sub-processors. Details: Security Policy, Privacy Policy, Data Processing Addendum.

Documentation and support

#