Jump to content

nasimg

Hornbill Users
  • Posts

    714
  • Joined

  • Last visited

  • Days Won

    13

Posts posted by nasimg

  1. Our instance is having problems today - it had a wobble 10 mins ago and just now (11:43).

    It has come back each time after approx 2 mins. We tested externally (on our iphones and got the errors).

    image.thumb.png.b4cf588379e37d52310f9874a2d42570.png

     

    When trying to open our service portal:

    image.png.13152689727b00b39c83d6941970e751.png

    Can you check the logs and see if anything can explain this (Health check and Status didn't show anything).

    Just to confirm it is ok now.

  2. Issue I have with 1. vs the others, is if you do anything other than resolving it with info on how to select the correct service/catalogue it, you may not have the info needed to complete the request. Plus you need the customer to raise it correctly next time.

    If they are simple request (and all the info is there) then 3 is good.

    Personally I would like the ability to edit the Service (I know this will be frowned upon by Hornbill)

    Nasim

  3. Following up this post as I can't see any replies...

    Doing more tests on the Change Calendar, Freeze periods are not visible in Internet Explorer.

    They are visible as a greyed out section in Chrome and Edge. The actual text only pops out when you view with the Day or Week option selected.

    Any reason why it doesn't work under IE or they pop up not working in Month view for the Change Calendar.

    Nasim

  4. We use the Hornbill mailbox (@live.hornbill.com) to send email updates/ resolutions emails to the customer. We also allow staff to update requests by replying to these emails via the routing rules.

    We do not want allow staff to raise new requests, or start conversations by sending to the mailbox as this channel is monitored.

    Is it possible to have a bounce back message sent if an email is sent to the mailbox that doesn't match any of our routing rules?

    Nasim

  5. Thanks @chaz

    But to confirm your changes work you need to choose midnight the following day - in your screenshot you have chose midnight at the beginning of the same day rather than the following day (ie the 23/06/2019 00:00)

    Ideally the "To" date/time shouldn't allow something before the "From" date/time - this would reduce the chance someone making the same mistake as you have done :D

    Nasim

  6. I've just noticed I can't select start/ end times around midnight in our change progressive capture

    Example:

    Start 20/06/19 23:00

    End   21/06/19 00:05

    It works if I select 01:00

     

    Can we also get an update for the defect PM00155911 - times for proposed start/end being 1 hour out.

    It has been outstanding for 2 months now :(

    Nasim

     

     

    Change time error.PNG

×
×
  • Create New...