Jump to content

Nanette

Hornbill Staff
  • Posts

    203
  • Joined

  • Last visited

  • Days Won

    12

Everything posted by Nanette

  1. @Gareth Cantrell@LawesD @davidrb84 @George Zippo @Martyn Houghton Apologies for the late response. We have identified a defect with updating existing FAQ;s, this is currently being investigated and will be addressed in a future release.
  2. @Caroline our developers are currently investigating this issue, we will provide an update as soon as one is available. Please bear with us.
  3. @Gareth Cantrell @HGrigsby Thank you for the post, our developers have fixed the issue and it will be available in the next Core UI build.
  4. @Gareth Cantrell The latest Service Manager Build has addressed the issue with the Missing Entity Explorer. Apologies for any inconvenience this may have caused
  5. @Adrian Simpkins@Gareth Cantrell We have rolled out a patch to your instance to fix the issue with the site field. However, if you encounter any further queries or concerns, please do not hesitate to reach out to us. We apologise for any inconvenience this may have caused and thank you for your patience and understanding
  6. @Nikolaj Apologies for the delay in addressing the issue you have encountered, upon investigation our team has identified a defect, We are actively working on a solution. They are now working to have it fixed. The fix will be available in a future product update.
  7. @Gareth Cantrell@Adrian Simpkins Our developers are currently investigating, we will provide an update as soon as one is available. Please bear with us.
  8. @Nikolaj The following setting within the Hornbill Admin section will need to be enabled to automatically add replied content. app.view.email.reply.includeOriginalMessageText
  9. We have identified a defect in this area, this will be addressed in a future release.
  10. @Jim is there a particular area that you are trying to search for the archived users?
  11. @Mike20 @Estie @Andrei Spiridon @samwoo @Gareth Cantrell We can confirm that the fix for this issue has successfully be deployed, the issue should no longer be apparent.
  12. @Mike20 @Estie @Andrei Spiridon @samwoo @Gareth Cantrell We have identified a defect in this area and are deploying a fix overnight to address this issue. Apologies for any inconvenience this may have caused.
  13. We are aware of this issue and our developers are investigating this with the highest of priorities, as soon as there are further updates, we will let you know. Please bear with us.
  14. @CraigP This link and the info below should help you clear the one that is stuck https://docs.hornbill.com/data-imports-guide/users/ldap/debugging Unable to run import, a previous import is still running This can occur if the previous import has failed to complete. Perform a manual (non-scheduled) run of the import from the command line including the argument -forcerun=true. Future imports should now run without issue.
  15. @Sana@Adam@Greggs@Alistair Young We have deployed a fix to resolve this issue. Apologies, for any inconvenience this may have caused.
  16. @Osman There's an option in the Admin section to search on Archived, Active, Suspended or All, are your using this for your search?
  17. Thank you. Our developers are looking into this and will provide an update as soon as we have any further information.
  18. Please can you provide the steps you have taken? Can you provide screenshots of what you are seeing?
  19. @Martyn Houghton@HHH@samwoo I'm afraid the change CH00157807 was pulled last minute and didn't make it to the release. Unfortunately, the release notes were not updated to reflect this. There is still a plan to do this in the future, no confirmed date as yet. The release notes have now been amended. Please accept our sincere apologies for any inconvenience this may have caused.
  20. @Berto2002 @Kelvin we can confirm this issue was addressed in the above release, there was an oversight in including this information in the release notes - Apologies!
  21. @Tina.Lapere this issue has now been fixed, you should be able to access Hornbill without any problems. Please accept our sincere apologies for any inconvenience this may have caused.
  22. @Tina.Lapere we are aware of the issue and are currently working on a fix. Please bear with us.
  23. This is being addressed under defect ref: KE00178558. Due to be fixed in the next Service Manager release.
  24. @Jim Are the emails that are being received for new requests or are they for requests raised before the Escalation Event had been deleted? Requests that use the service that the Escalation Events relate to, that were raised before the deletion of the Escalation Event will still fire.
  25. @Sam P@Berto2002@Will J Douglas@Mark Priest@lomixture We can confirm a fix has been pushed out to your instances to resolve this issue.
×
×
  • Create New...