We’ve released a powerful update to Tickler that gives you more visibility and control over your checklists—without needing to open each ticket.
What's new?
-
Advanced data export capabilities
-
Dynamic placeholders for real-time updates
-
Improved automation for fields and comments
-
A new base configuration template to simplify setup across lists
How they work:
1. Export checklist data using export_progress
You can now export progress to custom Zendesk fields using the new export_progress configuration.
You can surface:
-
The next task to be completed
- The last completed task
-
The overall percentage of list completion
-
A plain text summary of progress
- An HTML summary of progress
-
A version without task statuses
This is especially helpful for surfacing checklist status in Zendesk views, giving agents an at-a-glance understanding of what’s next—without needing to open every ticket.
2. Use dynamic placeholders for live updates
You can now use dynamic placeholders that reflect the current state of the list or all lists in the ticket:
For a specific list:
-
{{list.progress.text}}– Full progress as plain text -
{{list.progress.next}}– Next task to be completed -
{{list.progress.last}}– Last completed task -
{{list.progress.html}}– HTML-formatted progress -
{{list.progress.no_status}}– Progress without task status labels -
{{list.progress.percentage}}– Completion as a numeric percentage
Across all lists:
-
{{all.progress.text}} -
{{all.progress.next}} -
{{all.progress.last}} -
{{all.progress.html}} -
{{all.progress.no_status}} -
{{all.progress.percentage}}
3. Automate field updates at the tasklist level
You can now define actions at the list level, such as setting a field when any task is completed.
4. Automatically post updates to ticket comments
New support for posting comments when tasks are completed, skipped, or pending means your tickets can stay updated without any manual effort.
Note: This is only supported for automatic lists.
5. Define a base configuration for all lists with tickler_base_list
Reduce redundancy by defining a base list configuration that serves as a template for all other lists. This way, you avoid repeatedly adding the same configurations across multiple lists.
Example usage:
To see how to set these up, check out the updated examples in the Optional data fields and Automatic lists section of the Tickler user guide.
As always, your feedback is welcome through our support channels support@lovestockleaf.com or via the Support form.
Comments