When merging a ticket the one being merged unless filled in will be closed missing information. Since the ticket is being merged why not let it gain the (site, department, category, subcategory, and assignee)? This would not leave me having to fill in a number of tickets about to be closed, and does not fill my SLA full of…
This could be a little risky, but it would be nice to allow the merge function in automation rule actions.
User would like to opt out of receiving Service Desk satisfaction surveys, but there is no mechanism to do this under the individual notification settings or on their behalf in the admin controls.
All other areas of SWSD allows end users to copy/paste an image into the comment box. Chat doesn't have that ability, end users can only submit an attachment, that is a pain. This request is to allow end users to easily copy/paste into the chat.
Informational pop ups that can be triggered when selected ticket fileds are selected
could we please get the incident volume breakdown report (all reports really) key colors to be from largest to smallest like the report is setup
Hello! I would like to request a new feature to be present in the Automation rule actions section. Currently, you can set the action to update a record after a condition has been triggered. I am wanting to request the ability to "unassign" a ticket. Right now, the way I do this would be: Actions -> update record ->…
It would be very nice if we could have export to CSV options on more settings pages, like "Automation Rules" or "Notifications" because sometimes there are a lot of things configured in there and being able to export it and sort through it in a spreadsheet is easier than opening a bunch of tabs
When an end user adds comments to a closed ticket which it reopens the ticket. They can setup an automation rule to have the end user open a new ticket. Is there a way to disable the comment section so the end user is not able to add comments to a close ticket? They are aware they can choose to toggle off the "reopen…
Problem Statement Currently, the Subject field in the New Ticket window is a free-text field. This leads to:Inconsistent subject naming Difficulty in categorizing tickets Reduced reporting accuracy Slower triage and routing A structured and dynamic dropdown would significantly improve data quality, automation, and user…
It looks like you're new here. Sign in or register to get started.