Assume that you have Service Management project and you allow your customers to change Jira Issue status, while they don’t have Issue Edit permissions.
In that case, you may specify the proper user to run the post function and update the checklist who has proper permissions. Otherwise, the checklist won’t be applied as Customers don’t have edit permissions.
Option to copy checklist item's IDs
You can copy checklist item ID to use in your automation and integration scripts
Option to Enable/Disable Smart Checklist for new projects by default
You may define if a newly created Project will have Smart Checklist enabled by default or not.
Can't turn addon off for 10k projects
On instances with a huge amount of projects bulk addon enable/disable through addon Settings → Project didn’t work. Also, the checklist was enabled for only part of the projects.
We’ve updated the way how the page communicates to settings and introduced its own layer to proceed with bulk updates asynchronously.
CSV import doesn't work for Issue update
Importing checklists from CSV worked perfectly while adding a new issue. However, when updating the existing issue - it didn’t work. We've updated the way addon “listens” to a proper webhook. So now, bulk import checklist from CSV to the existing issue works properly.
Do not apply the default template for Closed issues
Customers were complaining that if there’s a default checklist set for a particular issue type - it was also applying to Jira issue that was already CLOSED.
We’ve changed that logic and now default templates might be added to a Jira issues in OPEN or IN PROGRESS states.
Checklist item details (quotes) are broken after release 5.2.0
When quotes (item details) added after checklist item w/o space between “>” and text - it hasn’t parsed properly.
Now, ither “>quote” or “> quote” are parsed properly.