Hi,
A feature that I would like to see is the ability to create an editable checklist for a ticket. This would be helpful if a ticket is, for example, a change request, that would involve multiple steps.
It would involve putting in a checklist at the top of the ticket, and being able to add, remove, check or uncheck individual checkboxes as needed.
See here, on microsoft planner:
I think a lot of users would benefit by a very simple but powerful ToDo-list feature.
Either as a custom object in the right ticket pane or as a additional tab in the right ticket pane. Ideally there is an option to enter āPresetsā so you can create a ToDo-list and save it for later. in the ticket, simple choose the preset from the dropdown and it will create the checklist in the ticket.
I like the idea of maybe 5-10 companies funding this feature request.
@thorsteneckel / @MrGeneration What do you need to give us a quote? Mockups?
I can create a requirenment form for this for our devs, but right now Iām not sure if this is applicable for a funding at this moment, Iāll need to talk to the team internally.
However, personally I donāt see another ātemplateā feature, Iād see it within the existing template functionality allowing you to define it during ticket creation. If you have a second templateish option, this will blow up the UI more which we usually try to avoid.
What do you think?
Also, right now Iām a bit short in time which is why this will take time.
I agree. The checklist could be placed at the bottom of the sidebar, where āTagsā and āLinked ticketsā are shown.
Ideally there would be a dropdown to load a predefined set of āToDosā with a button to save and load the presets. And then also an option to enter single checklist-lines and also to delete them.
I think both proposals are good. A todo list for changes. A general distinction between disturbances and changes would be perfect. In this way, the overviews could be clearer and slas for changes and faults could be defined differently. The running list is perfect when changes are processed one by one by different employees.
I would prefer an additional tab in the right ticket pane.
And yes this would be a very helpfull feature.
We also have a lot of tickets, in which we have to go through points on a to-do list at the right order.
These lists are very time consuming to work through, have many points on them and make our tickets crazily bloated, if we make a new comment every time a point is done.
So all in all our tickets tend to get really confusing, where a single checklist would be the better solution, especially if two or more agents are working on them.
Integrating other solutions like Microsoft Planner is just too complicated for our usage.
We would prefer an additional tab in the right ticket pane too. That should be the clearest solution.
Another option could be to change the specification of the ticket.object.
If we could set a ticket.object to a group, we could add booleans.
In my opinion that could be implemented as an easier method for a temporary solution.
I agree in the necessity to implement checklists and that they shouldnāt blow up the UI to make it less user friendly.
But checklists would definitely improve the productivity big time and we are strongly looking forward for implementation of this feature in the future!
Iāll keep an eye on the changelogs 
Is there any news on this? Are the devs working on this feature?
This topic was automatically closed after 416 days. New replies are no longer allowed.
This is a feature request on the community board - if you canāt find it on Github, the answer is no.
Adding feature requests to this board is no guruantee that a specific feature is adopted.
Please use the 
button on the first article to vote for this function.
This helps us to measure the need which is (currently) fairly low.
Hi,
any news on this idea and the funding option for the feature?
I see that some people like it and I know that other systems provide this option.
So maybe implementing it, could make zammad more attractive for organizations moving to zammad.
I know at least one company, the missing checklist is a showstopper for migrating to zammad.
We in generally do not communicate any ETAs or a roadmap if something is on the way.
If you want to find out the cost of this implementation you can always contact sales (at) zammad (dot) com to find out and, in case the cost is too high, ask for a group sponsoring.
Hello,
Zammad is a really nice project because itās not cluttered.
But I also wish for this function or a workaround for it.
It is important for our small support team to be able to quickly see which tasks are still open in a ticket.
Not all tickets can be ready within hours or days. A quick overview of what still needs to be done in a ticket would be great.
Who else needs this? Is group sponsoring a way?
Many Thanks.
Checklists/Checklist templates were very important to us as well. The workaround we are currently using in Zammad is setting up āMacrosā to add āTagsā for each Checklist itemā¦ exampleā¦ a Macro of āTask List - Checklist1ā that adds a predefined list of tasks to do (each task is actually a tag). Then when a task is completed, the agent just removes the tag from the ticket (zammad stores a history of task adds/removes in ticket). We also setup Overviews for the tasks to complete tags so an agent can check an overview to see if a ticket has a task for them to complete. It works well, but canned checklists would be better.
