We have a new documentation site. Please go here to see the latest.

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

This guide is based on Automation Lite for Jira provided by Code Barrel Pty Ltd. Please make sure that  Automation Lite for Jira plugin is installed in your Jira first. 

Prerequisites

"Save checklist data to Jira custom fields" option must be enabled in Issue Checklist Global Settings

Step by step guide

  1. Create a new rule in Automation plugin (go to Project Settings > Project automation and click Create rule button)



  2. Select "Issue Transition" as a trigger and next choose source and destination statuses (details of transition)



  3. Select Action as the next step and choose "Edit Issue" from the list of actions



  4. Select Checklist Content YAML field on the next screen



  5. Paste checklist in YAML format as presented on the screenshot, i.e.:




      - text: 'Acceptance criteria 1'
        checked: false
      - text: 'Acceptance criteria 2'
        checked: false
     Read more about YAML

    Unable to render {include} The included page could not be found.

    If you want to append checklist items, then put Checklist Content YAML field ID in double curly braces instead "items:" phrase in the first line, as explained in separate documentation page.

  6. Save the rule and test your setup (transition an issue and spot the checklist updated).
    If the checklist is not updated then please add Checklist Content YAML custom field to issue screen and check if it is correctly updated when issue is transitioned.
    1. If the Checklist Content YAML field is not updated (its content does not change) then please check the created rule, especially step 2 (source and destination transition) as the rule might not be started for given transition.
    2. If the Checklist Content YAML field is updated but the checklist panel (list of checkboxes) does not, then one of the following can be a reason:
      1. custom fields integration is not enabled (please enable it)
      2. the YAML provided in step 5 is invalid so it cannot be parsed and translated to list of checkboxes. Read more about YAML.
  • No labels