Using your views, you can make ticket updates to many tickets at the same time. For example, if you want to assign yourself to a number a tickets, you just select them in a view and then set yourself as the assignee. You can also delete, merge, or mark as spam the selected tickets. If you navigate to different pages, your tickets will remain selected.
Topics covered in this article:
Bulk updating tickets
The maximum number of tickets you can update at one time is 100 tickets. You cannot bulk update closed tickets. You can bulk update most of the same properties as an individual ticket, including ticket status, fields, subject, and comments.
For information about how specifying a default X (formerly Twitter) account affects bulk ticket updates, read about the Make this the default account setting described in Setting up your X (formerly Twitter) channel.
To update multiple tickets in a view
- Open one of your views and select the tickets you want to update.
You can pick and choose the tickets you want to update or select the entire list by clicking the check box at the top left of the view.
When you select one or more tickets in a view, a toolbar appears at the bottom of the list.
- Click Edit.
- In Edit tickets you can update ticket properties and add a comment for all of
the tickets you selected.
To help with accessibility, you can use keyboard navigation to select toolbar menu items and apply formatting before submitting the comment.
You can also apply a macro to all the tickets by selecting it from the Apply Macro menu. If you apply a macro that includes attachments to ticket comments, the attachments will not be included in the bulk update.
Note: If you bulk update tickets by applying a macro that uses dynamic content or placeholders in the ticket subject, then the updated tickets' subjects will be saved with the bracketed version of the subject. For example,{{ticket.created.at}}
may display in the subject instead ofMarch 2, 2023
.Most active ticket fields (including system fields, custom ticket fields, custom ticket statuses, and conditional ticket fields) display in the Edit tickets dialog box during a bulk update, regardless of the ticket forms applied to the selected tickets. However, the bulk editor doesn't support CC, followers, or @mentions.
For example, if you attempt to @mention someone from the bulk editor, the text in the comment remains plain text, and the person isn't CCed on the ticket. There's also no visible fields for CCs or followers in the bulk editor. You also can't use the bulk editor to apply macros that have an action to add a CC. The CC will not be added if the macro is applied this way.
- Click Submit to save your ticket updates.
When you make bulk updates to tickets (edit, delete, merge, or mark as spam), the event is recorded as a Web Service (API) update. See the example below. If you have triggers based on Ticket: Updated via conditions, make sure you take this into account.
Bulk deleting tickets
You can select multiple tickets in a view and delete them at the same time. Deleting a single ticket is described in Deleting tickets.
Once deleted, tickets are moved into a Deleted Tickets view, where you can restore them or permanently delete them. After 30 days deleted tickets are permanently deleted and removed from the Deleted Tickets view. You cannot bulk delete Closed tickets. For details, see Deleting tickets.
To delete multiple tickets in a view
- Open one of your views and select the tickets you want to delete.
You can pick and choose the tickets you want to delete or select the entire list by clicking the check box at the top left of the view.
- Select Delete from the toolbar at the bottom of the list.
- When prompted, click OK to confirm that you want to delete the tickets, which are then moved into the Deleted Tickets view.
Bulk merging tickets
You can select multiple tickets in a view and merge them into another ticket. Merging one ticket into another ticket is described in Merging tickets.
Be sure that you merge the correct tickets. Ticket merges are final. You cannot undo or revert a ticket merge. You cannot merge tickets with a ticket that's shared, or with one that's already closed.
- Open one of your views and select the tickets you want to merge.
You can pick and choose the tickets you want to merge or select the entire list by clicking the check box at the top left of the view.
- Select Merge from the toolbar at the bottom of the list.
Tip: Be sure to have the ticket number of the ticket you want to merge into handy before you start the merge process.
- In the Merge ticket dialog, enter the ticket number for the ticket you'd like
to merge the selected tickets into, then click Merge. Alternatively, you can
select a recently-viewed ticket.
If you’re attempting to merge tickets into a ticket with a different organization, brand, or requester, a message appears.
- Make sure that you aren’t unintentionally sharing sensitive information by merging the
tickets, then click Continue Merge.
- When prompted, click Confirm and Merge to confirm the merge. If you want to
cancel the merge, click Cancel instead.
Be sure that you merge the correct tickets. Ticket merges are final. You cannot undo or revert a ticket merge.
Bulk marking tickets as spam
You can select several tickets in a view to mark as spam and suspend the requesters. Marking a single ticket as spam is described in Marking a ticket as spam and suspending the requester.
Tickets marked as spam are moved to the deleted ticket view and the requesters are suspended at the same time. You can unsuspend suspended users if necessary.
To mark multiple tickets in a view as spam and suspend the requesters
- Open one of your views and select the tickets you want to mark as spam.
You can pick and choose the tickets you want to mark as spam or select the entire list by clicking the check box at the top left of the view.
- Select Mark as spam from the toolbar at the bottom of the list.
- When prompted, click Mark as spam to confirm the deletion.
Tickets marked as spam are moved to the Deleted tickets view.
64 comments
Cotton On (Online Customer Service)
Hi there,
When trying to bulk assign from one form to another, not all form names appear in the list - do we have a setting wrong?
0
Lou
Cotton On (Online Customer Service)
There is a check box in each form setup to associate to specific (or all) brands. Can you check that for a form you're trying to find?
0
Cotton On (Online Customer Service)
Thank you!
0
Carolline
Hey there,
When bulk editing a custom ticket field, I don't see an option to leave said custom field blank as it is possible when editing one single ticket. Am I missing something or is it really not possible? Any workaround suggestion?
Editing a single ticket:
Bulk edit:
0
Dane
This is currently expected for the Support ticket bulk update and the "-" option is only available for Dropdown fields. The only option that I can think of for other field is perform the update via Update Many Tickets API.
0
Peter Hochstrasser
Hi Carolline
How about "- Reset -" in the list above?
0
Carolline
Hi Peter Hochstrasser
I tried to use it, but it seems it only resets to the original value. For example, if I have multiple tickets each one with its own value, and I accidentaly change the value to X while bulk editing, if I hit "reset" this change is disregarded and all of the tickets keep the original value.
Dane not sure if I understand. These examples I gave are drop-down fields. The problem is with bulk editing (when editing a single ticket, I can clear the custom field just fine)
By the way - the workaround I could think of was setting up a trigger that fires when updating the ticket and including a specific tag. There's an option to clear the value of a specific custom field as an action for the trigger.
0
Kat
Is there a way to restrict permissions on bulk-editing tickets (like with merging tickets), so only agents with certain permission sets are able to bulk-edit tickets?
0
Anne Ronalter
Thank you for your Feedback.
A function to restrict the bulk editing for Agent is unfortunately currently not possible.
0
Kelly Schmiedeler
I bulk delete 200 tickets a day. Today this takes me a few clicks using the bulk delete app. Now I will have to delete them 30 at a time? Is that correct?
0
Audrey Ann Cipriano
Hi Kelly Schmiedeler welcome to our Community!
The in-product function for updating tickets allows you to delete a maximum of 100 tickets at a time :)
0
Bharath Bhushan M S
What is the workaround or fix for this?
We just can not "not" have this option. We need this working.
However, the bulk editor doesn't support CC, followers, or @mentions.
For example, if you attempt to @mention someone from the bulk editor, the text in the comment remains plain text, and the person isn't CCed on the ticket. There's also no visible fields for CCs or followers in the bulk editor. You also can't use the bulk editor to apply macros that have an action to add a CC. The CC will not be added if the macro is applied this way.
0
Peter Hochstrasser
Hi @Bharath Bhushan
Zendesk rewards the flexible and ingenious. In your use case, adding a tag works. Create your macro as a trigger that acts upon finding the tag set by its triggering macro... I know, I know - as we say in German, backward through the chest right into the eye - but that's Zendesk.
Cheers
Peter
0
Bharath Bhushan M S
Thank you Peter Hochstrasser, I unfortunately dont have the access to create a trigger and would have to reach out to admin team who is not in favor of creating multiple triggers. Is there any other workaround for this?
0
Arianne Batiles
Hi Bharath Bhushan M S,
Perhaps we can further discuss your problem via ticket. I will be sending you an email where we can continue working together. Kindly check your inbox for updates. Thanks!
0
Nikita Danilov
Hello,
We've recently encountered an issue where the bulk management checkbox has disappeared for one of our admin colleagues. It's worth noting that we both hold admin permissions and are viewing the same ticket view.
While I still have the ability to manage tickets in bulk, my colleague no longer sees this option. This change occurred quite recently on the colleague side.
We have already ensured that our admin permissions and view conditions are consistent. Is there any specific setting or configuration that could have caused this option to disappear for my colleague?
Your assistance in resolving this matter would be greatly appreciated.
Thank you.
0
Peter Hochstrasser
Hi Nikita
Did your colleague try to
- use another browser
- use a private tab or window?
If he does and still has the same problem, can you let him log into Zendesk on your machine?
I‘m trying to establish if the problem is with his account serverside, or if it is rather a cookie constellation or a browser specific problem that causes this.
0
Nikita Danilov
Hi!
We have identified the reason behind the disappearance of the 'Managing tickets in bulk' option in Zendesk. It appears that our custom software, which is used for quality checks and ticket tagging, is causing this issue. This software functions as a browser extension and is integrated with our website. It interacts with Zendesk and seems to be blocking the 'Managing tickets in bulk' option. We will address this issue on our end.
Thank you or your time looking into this!
0
Salokya Mathur
I am working on a client requirement where they don't want their agent to close ticket in bulk, Is there any way to hide the bulk edit option ?
0
Noly Maron Unson
Hi Salokya,
I'm afraid that the ability to edit tickets in bulk is not something that can be edited. This is a universal ability that is hard-coded into the system, and it is not linked to a specific setting or Role. If an agent has access to edit a number of tickets, they can modify them in bulk.
Hope this helps.
0
Sydney Neubauer
Our team would also like to remove the bulk edit option - there are too many things that can be changed that shouldn't be
1
Noly Maron Unson
Hi Sydney,
Though this is not natively possible at the moment, I've marked this comment as product feedback for review, which means that your input will be aggregated as a part of our Voice of the Customer program that provides customer feedback to our product development teams.
Thank you.
0
Akanksha Shukla
I am using an enterprise account, I have team members working based on the roles. Need help if my supervisor can re-assign the tickets to other agents in case the agent is offline or not available without even having the option to bulk update the fields and the other options apart from the assignee section. Can we disable the other field to be updated or edited?
0
Cheeny Aban
Yes, a supervisor may re-assign tickets to the other agents without bulk updating ticket fields. A user may select one or more tickets when viewing a list of tickets from a specific ticket view and make the assignment from there. Unfortunately, there is no native way to disable or restrict users from updating ticket fields. However, you may want to check for other third-party applications that have that capability. If you have other account-specific inquiries, you may also initiate a conversation with us so we can fully check them for you!
I hope that helps!
1
Akanksha Shukla
@... Can you suggest third-party applications for same?
0
Cheeny Aban
You may check our Zendesk Marketplace for apps. Thanks!
0
Megan (Envoy Consultant)
It appears that lookup relationship fields are also not supported in the bulk editor. Is that true? If so, is this on the roadmap?
0
Dainne Kiara Lucena-Laxamana
Hi Megan!
Yes you are correct that the ‘relationship field’ is not an available function when managing tickets in bulk. I think this would make a great product feedback request in our community forums!
We recommend you create a product feedback post about it here. You might also find this article on giving product feedback helpful: https://support.zendesk.com/hc/en-us/articles/4413820079386-Giving-Product-Feedback-at-Zendesk-. Conversations with a high level of engagement ultimately get flagged for product managers to review when they go through roadmap planning.
Specific examples, details about impact, and how you currently handle things are the most helpful things to share to help our product teams understand the full scope of the need when working on solutions.
We truly value customer feedback and your voice and votes in the product feedback topics in the community help influence future Zendesk functionality.
0
Luis Pérez
Hey there. Is there a way to tag the assignee of each ticket in bulk? I need to update hundreds of tickets by leaving an internal note with the name of the assignee so they get the notification. Like this:
@Name, please update the customer. But i need to do that for every ticket manually. Is there a way for me to automatically tag the assignee for each ticket in bulk?
Thanks.
0
Destiny
Thank you for reaching out. If I'm understanding correctly, you're looking to notify the ticket assignee in bulk when a ticket requires an update. Currently, the
@mention
functionality is designed for single ticket notifications and doesn't extend to bulk actions. However, you can use theticket.assignee.name
placeholder in an internal note and then reopen the ticket, which should trigger an email notification to the assignee.Unfortunately, I don't see any other features that fit exactly what you’re looking for at this time. I hope this suggested workaround is helpful. Should you have any further questions or require additional assistance, please feel free to reach out.
Best regards!
0