Content Comparison

Automation for Jira is a popular tool to get your team automated by creating additional workflows, rules, and processes.

...

Use Cases

Set Checklist on Issue Creation

...

1. Go to Automation for Jira → Automation Rules

   • 

2. Click Create Rule

3. Set When: New Trigger

   1. Choose Issue transitioned 

   2. Choose from status (e.g. Backlog) and to status (e.g. Selected for Development)

   3. Save

      • 

4. Add component New Action

   • 

5. Set New Action

   1. Choose Set entity property

      • 

   2. Choose Entity type: Issue

   3. Set Property Key

      • Code Block
        com.railsware.SmartChecklist.checklist

   4. Add checklist template items in Markdown formatting as the property value and add and add the following in the beginning: 

   Code Block
   {{issue

   .fields.Checklists}}
6. Image Removed

Alternatively, it is also possible to do the same via Issue Properties:

• Add checklist template in Markdown formatting as the property value and add the following in the beginning: 

...

1. .properties."com.railsware.SmartChecklist.checklist"}}

   Image Added

6. Save Action

7. Save and Turn Automation On

...

1. Choose the trigger Issue created

   1. 

2. Choose the action Create sub-tasks

3. List subtasks you need

   1. 

4. Click Add fields  - your subtask will be converted to a separate action step

5. Choose Same Project to be sure the sub-task is not lost

   1. 

6. Add "Checklists" custom field from Choose fields to set

7. Then add checklist items using checklist Markup formatting. Check the detailed guide.

   1. 

8. Save and publish the Automation Rule

9. Now when you create a Jira issue new sub-tasks will be created automatically

   1. 

10. Click on the one that contains the checklist  - see it's rendered with Smart Checklist add-on

    1. 

Add Checklist to Service Management tickets for certain Request types (not a JIRA issue type)

...

1. You would need to check what issue type you have for "Get IT help" requests

   • 

2. and And then create an Automation rule for this specific issue type. 

3. E.g. If you have a Request Type called "Get IT help" and it has "Service Request" issue type: 

   • 

4. In Automation, you would need to create a rule that would add a checklist to all the new “Get IT help” requests of "Service Request" issue type

   1. Set Trigger. When: Issue Created

   2. Image Removed

   3. Set Condition. If: Issue matches JQL 

      Code Block
      issuetype =

      '

      "Service Request

      ' 

      " AND "Customer Request Type" = "Get IT help"

      Image Added

   4. Set Action. Then: Set Issue Property

      Code Block
      com.railsware.SmartChecklist.checklist

      • And set the value of the checklist you need

...

1. Go to Automation for Jira → Automation Rules

2. Click Create Rule

3. Set When: Field value changed Change

   1. Choose Checklists → Save

      • 

4. Add component New Action

   1. Choose Set entity property

      • 

   2. Choose Entity Type: Issue

   3. Set Set Property Key

      • Code Block
        com.railsware.SmartChecklist.checklist

   4. Add the following to the Property value

      •  

   Code Block

   {{issue

   .Checklists

   .properties."com.railsware.SmartChecklist.checklist"}}

   Image AddedImage Removed

...

...

5. Save the rule and Turn Automation On

6. Proceed with the bulk update.

7. Once the bulk update is completed, turn the rule off.

...

1. Go to Settings → System → Automation for Jira → Automation rules.

2. Click Create rule.

3. Choose the trigger Field value changed, and choose Smart Checklist Progress as a field to monitor for changes. Save.

   

4. Set New condition → Advanced compare condition.

5. Fill First value → {{fieldChange.fromString}}, Condition → does not equal. Save.
   Here’s how it looks:

   

6. Set New condition → Advanced compare condition.

7. Fill First value → {{fieldChange.fromString.remove(“ - Done”).substringBefore(“/”)}}, Condition → less than, Second value → {{fieldChange.toString.remove(“ - Done”).substringBefore(“/”)}}. Save.
   Here’s how it looks:

   

8. Add Action → Create issue, Project → Same project, Issue type → Sub-task (or any other), Parent issue → Current issue, fill Summary and Description.

   

9. Save the rule and Turn Automation On.

Add Checklist Tab on Issue transition

With the Multiple Checklists feature, you can configure an Automation rule to add an existing checklist tab to the checklist when specific conditions are met. For example, when issue is transitioned from

1. Go to Project Settings → Automation → click Create rule
   

   Image Added

2. Create a trigger

2.1. Choose Issue transitioned

...

2.2. Choose From status (e.g.

Issue

com.railsware.SmartChecklist.tab.<tabID>

- Confirm client requirements are documented
- Schedule a feedback session with the client
- Collect and analyse client feedback
- Update the issue with client feedback outcomes

Issue

com.railsware.SmartChecklist.tab.<tabID>

{{issue.properties."com.railsware.SmartChecklist.tab.{tabID}"}}

## Definition of Done 
- **Code complete.** All code has been written and reviewed, and all necessary functionality has been implemented.
- **Code coverage.** All code has been tested and meets the required code coverage threshold.
- **Code quality.** Code has been written using the required standards, conventions, and best practices.
- **Integration.** Code has been integrated into the main branch and all integration issues have been resolved.
- **Security:** The software has been tested for security vulnerabilities and all issues have been resolved.
- **Performance:** The software has been tested for performance and scalability, and all issues have been resolved.
- **Peer review.** Code is reviewed by the peers.
- **System testing.** The software has been tested end-to-end, and all system tests have passed.
- **Regression testing.** All previously implemented functionality has been tested, and regression tests have been passed.
- **Documentation.** All necessary documentation has been written, reviewed, and approved, including user manuals, API documentation, and system documentation.
- **Acceptance testing.** The functionality has been demonstrated to the product owner or customer and has been approved.
- **Deployment:** The software has been successfully deployed to the production environment, and all deployment issues have been resolved.

## Definition of Done 
- **Code complete.** All code has been written and reviewed, and all necessary functionality has been implemented.
- **Code coverage.** All code has been tested and meets the required code coverage threshold.
- **Code quality.** Code has been written using the required standards, conventions, and best practices.
- **Integration.** Code has been integrated into the main branch and all integration issues have been resolved.
- **Security:** The software has been tested for security vulnerabilities and all issues have been resolved.
- **Performance:** The software has been tested for performance and scalability, and all issues have been resolved.
- **Peer review.** Code is reviewed by the peers.
- **System testing.** The software has been tested end-to-end, and all system tests have passed.
- **Regression testing.** All previously implemented functionality has been tested, and regression tests have been passed.
- **Documentation.** All necessary documentation has been written, reviewed, and approved, including user manuals, API documentation, and system documentation.
- **Acceptance testing.** The functionality has been demonstrated to the product owner or customer and has been approved.
- **Deployment:** The software has been successfully deployed to the production environment, and all deployment issues have been resolved.