You might find Smart Checklist integration with ScripRunner useful for updating checklists using automated scripts.
Since we use Issue Properties as primary memory storage for checklists, it's required to update Issue Property to have checklists updated with any type of automation. Updating "Checklists" Custom Field won't bring the desired result. We are in touch with ScriptRunner support to identify if it's possible to do via scripting in the current implementation.
However, if the issue has no checklist set yet - it's possible to initiate initial rendering by pushing value to the custom field.
Set Checklist depending on Custom Field Value after Issue Creation
If you want the specific Checklist appended to your newly created ticket depending on the other Custom field value - you can easily do it by adding Script Runner Post Function to your Create Ticket workflow transition.
Check it out!
Assume that you have a custom field named "Environment" with 2 values: Production/Staging. So you expect that while adding a new issue - you'll have a proper checklist assigned
Go To Workflow Editor
Choose "Script Post Function" Script Runner
Choose "Custom Script Post Function"
Add inline Script
Variables checklistProd and checklistStage used for keeping the proper value of the checklist (in text format)
Save the script. IMPORTANT! Make the Post Function is placed as a #1 Step!
Customize checklist visibility by user group/ user role/ ticket type
ScriptRunner can be used for hiding separate UI elements on your Jira tickets depending on different conditions. This way, you can hide Smart Checklist visibility on your Jira instance for specific user groups/ roles/ ticket types.