On this page:

How to use the Didit actions in Jira Automation

Didit adds three actions to Jira Automation, so your rules can work with checklists without properties or JSON. They act on the work item that triggered the rule, in project and global rules.

Add a Didit action to a rule

  1. Create or open an automation rule and choose a trigger, for example “Work item created.”

  2. Click the ”+” below your trigger, choose “Action,” and search for “checklist.” The Didit actions appear under “Other apps.”

    In older rule builders, click “Add component → THEN: Add an action.”

    The Jira Automation rule builder with "checklist" typed into the action search, showing the three Didit actions under Other apps.
    The Jira Automation rule builder with "checklist" typed into the action search, showing the three Didit actions under Other apps.

  3. If Jira asks you to connect Atlassian Automation to the Didit app, click “Connect.” One connection covers every Didit action in the rule.

    The Create checklist from template action panel asking to connect Atlassian Automation to the Didit app, with a Connect button.
    The Create checklist from template action panel asking to connect Atlassian Automation to the Didit app, with a Connect button.

  4. Fill in the action, as described below.

  5. Name the rule and turn it on.

Create checklist from template

Creates a checklist from one of your Didit templates. Search for the template by name, or paste its ID if it doesn’t show up. Then choose what happens if the work item already has a checklist.

The Create checklist from template action form with the Definition of Done (DoD) Checklist template selected and Replace chosen under If a checklist already exists.
The Create checklist from template action form with the Definition of Done (DoD) Checklist template selected and Replace chosen under If a checklist already exists.
If a checklist already existsWhat happens
ReplaceReplaces the existing checklists with the new one.
AppendAdds the template’s headings and tasks to every existing checklist. The template’s metadata is ignored, and completed tasks stay as they are.
AddAdds the new checklist next to the existing ones.
FailCreates no checklist.

Create checklist from markdown

Creates a checklist from Markdown you write in the action. Start with a # line for the title, then add a ## line for each heading and a - line for each task. Smart values like {{issue.summary}} work too.

The Create checklist from markdown action form with a release checklist in the Markdown field: a title, two headings, and three tasks.
The Create checklist from markdown action form with a release checklist in the Markdown field: a title, two headings, and three tasks.
  • The action always replaces the checklists on the work item. To keep them, use Create checklist from template with Add or Append.
  • Keep hyphens out of the title line: Didit turns the text after a hyphen into an extra task. Work item keys contain a hyphen, so don’t put {{issue.key}} in the title.
  • Task descriptions aren’t supported.

Set checklist metadata

Fills a metadata field on the work item’s checklist, so the checklist needs metadata. Enter the field name exactly as it appears on the checklist, and a value: text or a smart value like {{issue.summary}}.

The Set checklist metadata action form with Employee Name as the metadata field name and the issue summary smart value as the value.
The Set checklist metadata action form with Employee Name as the metadata field name and the issue summary smart value as the value.

Tips