💡Submit your feature requests, 👍 vote on others, and 🔔 subscribe for updates.
Help us prioritize what’s next for Smart Checklist!
Allow selection of assignee/due date when using Linked Templates
We are looking to use checklists to ensure process is followed across multiple projects in our team. We want to use Linked Templates so that the checklists are consistent. Each project will have a different team working on them. Currently we cannot use the Assignee or Due Date concept as these are part of the template, and not able to be set on the individual checklist items when added to a ticket. This would mean we would need the same Assignee on all projects which is not practical for us. Idea is to allow Assignee and Due Date to be set per instantiation of the checklist when added onto a ticket. Even better if we could also write automation rules to modify the assignee and due date.
JQL to match count of mandatory items
Scenario is a checklist with some items mandatory, and some optional. I want to create a dashboard widget that shows a list of the mandatory items that are not complete. I cannot see a JQL function to return those.
Ability to search issues by Template ID via JQL
Currently, there's no way to locate all tickets that were created using a specific checklist template. JQL doesn't support searching by Template ID, which makes it difficult to audit or report on template usage across projects. Proposed solution: Add support for querying Template IDs directly in JQL, similar to: SmartChecklistTemplateId ~ 14 This would allow admins and users to quickly find all issues associated with a given template, which would be especially useful for auditing, reporting, and cleanup tasks at scale.
Update checklist from customer portal
Provide the ability for users update checklist from customer portal directly.
Option to activate SmartChecklist on every issues from every projects
As of now, when migrating to Cloud, Smart Checklist needs to be reactivated manually on every projects, either done by an admin before delivery to the client, or done by the client’s teams post-migration. Would it be possible to have a button on the administration side to automatically activate (and show) the add-on on every projects where the Smart Checklists fields are presents on the screens ? Best regards
Due Dates reminder notifications
Use case is a checklist item that is assigned to a user, with a due date. It would make it easier to manage checklists if there could be a reminder notification to the assignee of the checklist items that are assigned to them as the due date draws near. I could imagine two forms of this policy: Where a user gets a notification for all the checklist items coming due on a single ticket. A digest form where a single notification lists all Jira tickets with a checklist item open to them, listing each checklist item under its parent ticket.
Rename default statuses per Project/Space
The default fixed status values (Todo, In Progress, Done) do not always suit every task in a checklist. Sometimes the question might be better answered with Yes, No, Not Applicable. It is possible to add these custom Status values, but they cannot replace the fixed status values. This means users see a complex list of the fixed and custom values and there is no control on what is valid for a given question. It would be good to allow ideally a checklist question to specify what Status values are permitted, and only offer those in the selection. Even a simpler feature allowing replacement of the default status values per Space would be beneficial. Perhaps still requiring a state to map to the principals of Todo, In Progress, Done but using the admins term instead.
Checklist Comments
Ability to add comments to checklist item (don’t confuse with detailed information). A user could comment on a item from the checklist to provide more context about the status of that specific item
Restrict Completion of Checklist Item to Assignee
Restrict the checklist so that it can only be checked/unchecked by a specific assignee
Checklist Table/Add Columns to Checklist
It would be useful to allow a grid for checklist items, rather than a single line. See arbitrary example image of what resulting formatting might look like.
Support custom fields for Advanced template conditions
Add support for custom fields to be added to their own templates under advance automations.
Support Grouping by Issue Fields in Dashboard Gadgets
Currently, you can group group dashboard by using assignees, type of tickets, status, etc. We propose adding the option to allow grouping by custom field on an axis and then by status on the other.
Support Custom Checklist Statuses in the "Set Checklist Item Status" Automation
Currently, the Set Checklist Item Status automation action only allows selecting from the four predefined statuses. However, Smart Checklist custom checklist statuses are not available when configuring automation rules. Users should be able to select from all statuses available in the checklist configuration for the project/instance, including custom statuses.
Strikethrough completed items text
Displays text crossed out when item is checked. Option to choose, what we want.
Ability to hide specific checklist sections or items by user groups.
Add the ability to show or hide checklist sections in the Jira issue view based on user groups.
Allow Managing Template Categories in Cloud
Add the ability to manage template categories in Cloud by renaming or deleting them. This would help users keep their workspace organized and prevent the display from becoming cluttered with duplicate or outdated categories.
Add a reference to know the template on automation flow actions
When we use a template in an Automation flow (former automation rules), the only thing we can see is the ID of the template. Not even the name. Then to know what the actual template is, we need to check one by one to find the ID. There should be a direct link to the template, or at least the name and scope, so we can easily debug those actions.
Organize Checklist Templates
Add the ability to organize checklist templates more efficiently: reorder templates and sort templates alphabetically for easier navigation.
Next Up
Do not allow Project Administrators to manage Global Templates
Prevent Project Administrators from being able to manage Global Templates: Only Jira Administrators should be able to create, modify, and delete global templates Project Administrators should be able to view and import global templates, but not modify or delete them