now task users see the requester but it is the assignee , make the task users see the real requester and add columns or customize the view as needed
Currently, there is no way to manually rearrange or reorder tasks attached to Incidents, Requests, and Changes based on personal criteria after the insertion. Tasks are listed with the most recently added at the top, which is not ideal when planning activities. It would be helpful to have the ability to move each task as…
-Customer would like to deploy the SolarWinds Discovery Agent on MacBook devices. However, for deployment purposes, they require the installer in .pkg format instead of .dmg. -They had tried all possible workarounds. The only step they haven’t attempted is deploying a .pkg file. However, this requires the App Bundle ID…
Have a flag in the category section; if a category can be viewed when submitting an Incident or Service Request. Choose to have it available in both, one or the other. Our organization has more than just IT utilizing the system while trying to make the experience for the end-user as easy as possible. Strategic wording to…
I'm trying to make a report that excludes 1 or 2 specific categories / subcategories, and right now the only way for me to do that is to select every category except the ones I want to exclude. The bigger problem with this is that if we later add categories, I have to remember to add the new categories to this report. It…
Hi SolarWinds Team, I’d like to submit a feature request for Procurement / Purchase Order notifications in SolarWinds Service Desk. Currently, Automation Rules only allow scopes for Incident/Service Request, Change, and Asset, and the Notifications section does not provide options for Procurement events. This makes it…
As I am using SolarWinds Service Desk, I’ve found the platform very effective for managing incidents and service requests. However, one key capability that’s currently missing and would greatly enhance service operations is support for Operational Level Agreements (OLA) and Underpinning Contracts (UC). These features are…
We recently migrated to the ESM platform. And though we appreciate the ability to forward an incident to another provider, we have thousands of legacy incidents that need to be migrated to the newly created providers. Forwarding each incident individually would take a tremendous amount of time. I would also recommend that…
We have solar winds service desk service requests that need tickets to end up in a different category or subcategory during their lifetime. So a case starting out with a more general assignment: Needs to change so a different group of techs can see and act on the ticket: We already handle the updates of "assigned to" and…
It looks like you're new here. Sign in or register to get started.