Jump to content

Deen

Hornbill Staff
  • Posts

    783
  • Joined

  • Last visited

  • Days Won

    30

Everything posted by Deen

  1. This does not appear to be linked to the Mail related issues seen on Monday last week. Most likely linked to the performance issues now addressed on the request that was raised.
  2. @Adrian Simpkins I am not aware of any feature unfortunately that would allow you to have Supportworks style numbers against each timeline update. Personally I just have them in order of most recently posted.
  3. @StephC That's good to hear thanks.
  4. @Mark (ESC) One other thing to check is the visibility level of the timeline update. If the updates are defaulting to 'Team' they will not trigger an email notification. They need to be set to 'Customer'.
  5. @Shamaila.Yousaf I believe the main board view does contain a filter, also from what I can see the individual boards also have a number of pre set filters such as User, Attachment etc.
  6. @Andrew Tasker There were performance issues with the database on your instance at that time however that should now have been corrected earlier this week. Let me know if problems persist however.
  7. @davidrb84 A fix was rolled out earlier this week, let me know however if problems persist.
  8. The above was due to the receiving mail server rejecting the connection, so the mails aren't sent and remain in the outbox. After a number of attempts the connection is accepted and then the emails begin to move again.
  9. @Paul Morrow I can hide specific posts of yours if that is what you require?
  10. @StephC @HGrigsby How have you managed implemented Steve's workaround? Let me know if you have had any problems with this.
  11. @Mark Priest Could you let me know if this is now back up and running for you as we have deployed a fix.
  12. @Andrew Tasker We are looking into the root cause of this and I will have an update for you shortly.
  13. All, we are looking into the root cause of this and I will have an update for you shortly.
  14. @RobW There was an issue yesterday whereby one of the databases became unresponsive at that time, we are still looking into the root cause of the database problems however we do know that it is the root cause of your email issues. We will provide additional info when we have it.
  15. Possibly a caching issue, but good to know it is now no longer occurring.
  16. @nasimg If they switch to a different browser does the problem still occur? Also it would be worth flushing the browser cache to see if that makes a difference.
  17. Looking at the database it appears that the tag's are stored in the h_tag table. This table holds generic tags for other areas of the application also and is not limited solely to asset tags. So you will need to filter down the data here. For me I had to filter by h_tag_group which was 'urn:tagGroup:serviceManagerAssets'. Also h_tag_links stores the relationship between Tags and Assets. When retrieved via Database Direct there is an export button in the query tool to export results.
  18. A fix has now been deployed and the problem should no longer be occurring. Let me know if this is not the case however. Apologies for any inconvenience this may have caused.
  19. We have noted the issue and are currently investigating. I will post an update up shortly with our progress.
  20. We have identified the root cause of the issue and are currently working on a fix. I'll have a further update shortly.
  21. @JAquino Not from what I can see, it may be the case that you will need to carry out another import with the amended data and the import set to update the existing asset records.
  22. As you say the FAQ's are sorted by the date they were added. I cant see a way of changing this unfortunately without going down the enhancement route.
  23. Thanks for letting us know Kelvin, I'll close off the corresponding support request.
  24. @HHH Not from what I can see unfortunately, these appear to be hard coded. Perhaps something that can be considered as an enhancement.
  25. After additional investigation it appears that this issue was caused by a defect in Project Manager. This has now been corrected and the fix will be present in the next release.
×
×
  • Create New...