Open for Voting

Make Tech Group "Force E-Mail Notification To" Settings Also Apply to Manually Assigned Tickets

This request relates to changing how the "Force E-Mail Notification To" feature works for Tech Groups (Setup>Techs>Tech Groups>Tech Group Levels):

It pains me to know that in Web Help Desk the "Force E-Mail Notification To" feature highlighted above, applies only to tickets assigned to a tech group in just the narrowest of situations as detailed in the Help File:

The notification is sent to one or more Techs (depending on the selected option) only when:

  1. A Client updates a Ticket
  2. A new Ticket is created by using REST API
  3. A Ticket is updated by using REST API
  4. A new Ticket is created from the SolarWinds alerts it accepts
  5. A Ticket is updated from the SolarWinds alerts it accepts

This means that the feature as designed, is absolutely useless in situations where a ticket is simply MANAULLY assigned to a Tech Group by a human.  I've submitted at least two Help Desk tickets suggesting that the feature "as designed" is absolutely the dumbest, as I know absolutely NO organization out there that would ever say to me "Oh no...if a customer assigns a ticket to my team (or if automation via REST API or SoloarWinds Alerts sends the group a ticket) please send notifications.  BUT if a Human sends my team a ticket...NO...don't send notifications."

Nobody says that...nobody.  So the fact that the "Force E-Mail Notification To" feature isn't programmed to be able to handle sending notifications for when both HUMANS --OR-- AUTOMATION sends a ticket to a Tech Group?  Is just so bizarre and weird and smacks of bad programming crafted by very narrow minded thinkers.

This feature request is to modify the feature so it works as indicated below:

The notification is sent to one or more Techs (depending on the selected option) only when:

  1. A Tech Assigns an Existing Ticket to the Group
  2. A Client updates a Ticket
  3. A new Ticket is created by using REST API
  4. A Ticket is updated by using REST API
  5. A new Ticket is created from the SolarWinds alerts it accepts
  6. A Ticket is updated from the SolarWinds alerts it accepts

Otherwise, in situations where a Ticket is assigned to a Tech Group manually by a human...this feature as designed leaves you completely incapable of sending automatic notifications to:

  1. The Tech Group Manager
  2. Level Techs when no Tech is Assigned
  3. ALL Level Techs regardless of who the ticket is assigned to

As designed and assuming you have no automation enabled (you're not using REST API or SolarWindws Alerts), notifications will only ever be sent if a customer creates a ticket that uses a Request Type that's programmed to route the ticket to the Tech Group --or-- a customer updates a ticket that's already assigned to the Tech Group.

All other scenarios require there to be some type of automation in place (i.e. REST API or SolarWinds Alerts) in order for notifications to be sent. 

This is truly a bogus feature as designed and it's why it needs to be changed as described above.

The sooner the better...and it sorrows me that I even need to ask for this feature.  Please vote for this idea today!