The most recent content from our members.
There should be a switch that allows us to make the technician you're able to select dependent on the Group the ticket is assigned to. For example, if I have a Network group with John, Jane, and Joe as members, when I change the Group Assignment of a ticket to that Network group, I should only be able to select John, Jane,…
Based on Forum discussion here: (+) Are you able to add an assignee based condition and action to an SLA? - Forum - SolarWinds Service Desk (SWSD) - THWACK
When using Process Integrations/using Solarwinds API to generate child tickets from parent tickets, there's currently no way to grab the attachment or assignee from the parent ticket and transfer that value to the child ticket(s). I was able to perform a workaround for attachments by using an "Attachments" type custom…
Today, there is a scope option for "Assignee: -- Assignee --" that dynamically filters Incidents based on the user. Having this same functionality for the user's Groups would be wonderful. In the current configuration, our only alternative is creating multiple identical roles and scoping each group individually. This could…
We would like the ability to assign an incident to be separate from the permission to manage it. i.e., a T1 can reassign one of their tickets to a T2, but they can't see or edit the T2's tickets.
We'd like the ability to remove the "Not Set" option for the "Assigned to" so that tickets do not get assigned to no one.
I am trying to make the tech assignment a required field before it is resolved or closed. I have noticed some techs closing tickets without assigning it themselves and this will skew monthly reports.
It looks like you're new here. Sign in or register to get started.