feature request for deleting all or some part of a group of tickets
ART-2873_KNOWLEDGE_NODE-24
[Snap-ins](/docs/snapins)\n[Automate](/docs/automate)\n[Bulk delete data](/docs/automations/bulk-delete)\n\nBulk delete data\n================\n\nThe bulk delete data snap-in allows users to quickly delete multiple tickets, issues, accounts, or contacts in DevRev. By using a command-based approach and tag-based filtering, it ensures efficient data cleanup while maintaining reliability. Furthermore, access control options are included to prevent the feature from being misused.\n\nThe following
Bulk delete data | Automate | Snap-ins | DevRev
ART-2873_KNOWLEDGE_NODE-28
following command:\n\n```\n```\n1 /bulk_delete\n```\n```\n\nSelect the <data\\_type> among one of the following:\n\n* Tickets\n* Issues\n* Accounts\n* Contacts\n* Opportunities\n* Articles\n\n1. After entering the command, select the object type you want to delete from the list. Tags linked to these objects will be displayed for confirmation.\n2. The repurcussions of deletion will be informed to the user before they are allowed to confirm whether they wish to proceed with the deletion.\n3. The
Bulk delete data | Automate | Snap-ins | DevRev
ART-2873_KNOWLEDGE_NODE-27
are displayed in the timeline, including successful and failed operations.\n\nHow to use bulk delete data\n---------------------------\n\n![]()\n\nAccounts cannot be deleted unless all linked tickets are unlinked first.\n\n1. Add the **Bulk Delete Data** snap-in from the DevRev Marketplace to your environment.\n2. Select the tags you want to use as filters for the data deletion. These tags will determine which items are eligible for deletion.\n3. In the timeline of any object, type the
Bulk delete data | Automate | Snap-ins | DevRev
ART-2873_KNOWLEDGE_NODE-25
fields are mandatory:\n\n* **Tags**\n* **Object Type**\n\n![]()\n\nDeleted data cannot be recovered.\n\n![]()\n\nIf items were imported via an active AirSync, the deletion will cause the sync to fail.\n\nFeatures\n--------\n\n* **Command-based workflow:** Initiate deletions by using the /bulk\\_delete command in the timeline.\n* **Tag-based filtering**: Only items matching the selected tags are deleted, providing precise control over the process.\n* **Access Control**: Ensures only authorized
Bulk delete data | Automate | Snap-ins | DevRev
ART-2873_KNOWLEDGE_NODE-26
users can perform deletions, this can be defined in the configuration.\n* **Confirmation prompts**: Ensures users explicitly confirm whether they want to proceed with deletions, minimizing accidental actions.\n* **Parallel execution**: Deletions are performed concurrently, ensuring fast and efficient data processing.\n* **Error handling**: Failed deletions are logged, and feedback is provided directly in the timeline for review.\n* **User feedback**: Detailed summaries of the deletion process
Bulk delete data | Automate | Snap-ins | DevRev
ART-1824_KNOWLEDGE_NODE-446
with any of the provided channels.\nAllowed values: email plug slack twilio twilio_sms\nticket.group string Optional\nFilters for tickets belonging to specific groups.\nticket.is_spam boolean Optional\nFilters for tickets that are spam.\nticket.needs_response boolean Optional\nFilters for tickets that need response.\nticket.rev_org string Optional\nFilters for tickets that are associated with any of the provided Rev organizations.\nticket.severity enum Optional\nFilters for tickets with any of
Delete — DevRev | Docs
ART-1981_KNOWLEDGE_NODE-10
- [Bulk delete data](/docs/automations/bulk-delete)\n    - [Bulk work item uploader](/docs/automations/bulk-upload)\n    - [Commands surface expander](/docs/automations/commands-surface-expander)\n    - [Convergence](/docs/automations/converge)\n    - [Conversation reminder](/docs/automations/conversation-reminder)\n    - [CSAT on conversation](/docs/automations/csat-conv)\n    - [CSAT on ticket](/docs/automations/csat-tickets)\n    - [CSV work item
Support best practices | Computer for Support Teams | DevRev