Setting up a Checklist Workflow Condition

You need administrator rights in Jira to perform the tasks on this page.

You can use the Checklist Workflow Condition to enforce a specific level of checklist completion before a workflow transition occurs. If your custom rules are not met, the transition cannot be initiated.

Although validators can achieve this same effect, the key difference is that with a condition, the transition button will simply not be available.

To learn more about configuring workflows and workflow conditions, see the Atlassian Jira documentation.

To create a custom condition:

  1. Go to Administration > Issues.

     

  2. In the sidebar, go to Workflows > Workflows.

     

  3. In the Actions column for an existing workflow, click Edit.

     

  4. Select the transition that you want to modify:

    • In Diagram mode, click on the arrow that points to the transition, and then click Conditions in the panel that appears on the right.

       

    • In Text mode, click on the transition name in the Transitions (id) column.

       

  5. In the Conditions tab, click Add condition.

     

  6. Select Checklist Workflow Condition and click Add.

     

  7. Configure the parameters, which are described in the table below, and click Add.

     

  8. On the Workflows > Workflows page that you are returned to, publish your edited workflow so that your changes take effect.

Setting

Description

Setting

Description

Checklist

The checklist(s) to which the condition will be applied; use Shift + Enter or Ctrl + Enter to select multiple. If none are selected, the condition will be applied to all checklists associated with the issue.

Validation type

The type of validation that will be performed on the checklists:

  • All items checked: Validates that all items are checked.

  • All mandatory items checked: Validates that all mandatory items are checked.

  • Number or percentage of items checked: Validates that a specific number or a percentage of the items are checked. Enter either a round number (e.g. 2) or a number with a percent symbol (e.g. 25%).

  • Number of existing items: Validates that the checklist contains a specific number of items.

  • All items must have a status: Validates that all items have a status.

  • All mandatory items must have a status: Validates that all mandatory items have a status.

  • All items must be assigned: Validates that all items have an assignee.

  • All mandatory items must be assigned: Validates that all mandatory items have an assignee.

Validated items

The checklist items that will be validated:

  • All items: Validates all items in the checklist (both local and global).

  • Only global items (options): Validates only the global items in the checklist.

Conditional rules

The issue rules that must all be satisfied before the condition will be applied. If no issue rules are created, the condition will always be applied.

  • JQL Query: The issue must be returned by the specified JQL query. If you enter a specific JQL query instead of using a filter, click Validate to ensure that your syntax is valid and that no errors are returned.

You can use an %issuekey% variable in your JQL query to inject the key of the current issue, which is useful for special JQL functions like the ones used by ScriptRunner. If you do so, you can enter an issue key in the Issue Key placeholder field to inject into the variable for the purpose of validating your query.

To make a filter appear as an option, mark it as a favorite.

  • Issue Label: The issue must have at least one of the specified labels.

  • Issue Type: The issue must be of the specified type(s).

Panel display modes limitation

In the Independent panel and Sidebar panel display modes, the workflow buttons in the operations bar (see image below) will not update when the checklist is edited. If you still want to use the panel display modes, we suggest using a Checklist Workflow Validator instead.

 


SERVER documentation (On Cloud? Go here.)
Have questions? Contact our Service Desk for help anytime.