Jump to content

Deen

Hornbill Staff
  • Posts

    784
  • Joined

  • Last visited

  • Days Won

    30

Posts posted by Deen

  1. @Alberto M I cant see anything in the application settings that would treat escalation updates differently to other non owner updates.  The only potential way around this that I can see would be to disable the following so that the escalation doesn't actually post to the timeline.

    Post to Timeline - Tick if you want the notification text to be posted on the timeline of the impacted request
     
    • Thanks 1
  2. @Adrian Simpkins if the email is not actually reaching Hornbill, there is no mechanism that I can see in Hornbill which would then be able to send a bounce back as it would have no knowledge of the email.  It's probably reaching the mailserver and residing there.  The following may be of use in setting this up:

    https://docs.microsoft.com/en-us/exchange/mail-flow-best-practices/non-delivery-reports-in-exchange-online/non-delivery-reports-in-exchange-online

     

  3. @Alisha disregard the above for reports, as _itsm_request_team_assignment  is a separate table  that contains the info you are after.   The h_assignment_timestamp field will contain the assignment time and h_team_id the team it was assigned to.

    • Thanks 1
  4. @Alisha although there is a field in the database that specifies what team the request resides with, I don't see one for when it was assigned so that would make a filter problematic.  There is also the issue of the request potentially being reassigned several times during its life cycle. 

×
×
  • Create New...