Jump to content

Jim

Hornbill Users
  • Posts

    395
  • Joined

  • Last visited

  • Days Won

    7

Posts posted by Jim

  1. Hi, 

    I have an issue with our Service level agreements and the timers not setting accurately, when using 'days' in the service level it seems to be using a count of 24 hours to be one day based on the work time calendar opposed to calendar days, for example a SLA of 2 days response and 4 days resolution Logged on the 07/03/23 09:55  are being set to Resolution of 14/03/23 15:55 and Resolve of 22/03/23 13:25

    Our calendar operates 8.5 hour days Monday to Thursday and 8 hour days on a Friday, when calculating the dates it is using 24 working hours as 1 day

  2. Hi Steve, 

    Thank you for the response, 

    In my scenario If I send an email in the 'To' section to 5 different people and then 'cc' in another 2 people it will only show the 2 that were cc'd in, So when we send emails to a user and there manager you can't see this in the updates that the manager was included in the Timeline updates 

  3. At the moment when suspending and waiting I have to choose a specific action to watch, in my scenario I am waiting for an update and if it meets certain criteria it will go into a Major incident process, If a request is resolved it will still sit waiting for the update, I have set an expiry time to handle this however it is not the est solution as a resolution notification won't be triggered until the time expires.

  4. Hi @Berto2002

     

    I personally would recommend using an escalation event within the high priority service levels and making sure either some or all users have the 'Advanced Request Task Completer'  service desk right 

    as below I can send a notification to the owners manger and set a time it will trigger this so if there is 1 hour left to meet the resolution target time or resolution etc 

    image.png.1f9449ed4fec75181730398751183dde.png

     

    In terms of a report maybe you could filter based on priority and is not resolved and then check the timestamp of the last update by joining the requests table to the h_buz_activities table to get a time stamp and then set a time range of what is considered an inactive request? 

     

    • Like 1
  5. Hi, 

    I am having an issue where raising a new linked request is copying the custom fields from the initial request and ignoring all of the new information filled in through the intelligent captures

    You can see in the questions section I entered different information on this request but the custom fields in the details section show the information provided in the initial request

    image.png.7ab9536b6f1c89d18a23f151439ae541.pngimage.png.304ba455ae4f6aee420bc7f3d3d4d1fa.png

×
×
  • Create New...