Aaron Summers

+1

+1

Confirmed we are back up and running now Speedy job Hornbill!

Yeah, Hornbill Status site which say the same thing as yours @John C I am talking about this: https://www.hornbill.com/support This show an error

@John C mine say the same thing, status all okay however if you check Hornbill - Get Support, status health check failed for us.

Same for us too

Back up for us

Ditto

We would be fighting over it for being the first in the line! have a good break @Gerry! Aaron

@HHH We did that before but we abolished that rule because most of the time it actually useful to received as they usually confirm the date to return to the office so that we can change the ticket date on hold for longer or shorter duration. So we add another node to put the ticket on hold after "autoreply" emails came through. it still have hit and miss process but It works Aaron

@Dan Munns I have not come across to that project for doing RAID 10 yet but it will be my goal at the moment. What type of RAID 5 have you setup with and what memory did you used? Wonder whether you go for brand or for actual component that do the job far better at cheaper cost? I have not met anyone that have RAID setup (in fact any RAIDs), so I am more curious about it, even though there are ton of information out there but I want to hear from actual people that have and done the process with RAID. Would you use RAID for gaming, speed performance or work related purpose? Aaron

Issue resolved as it turned out that @samwoo changed Capacity to TIll Manager (For Application purpose with chip and pin devices). So he have changed it back to Capacity. Can close this post now. Aaron

+1 for us @yelyah.nodrog Our workaround for this is to suspend the ticket and ONLY change it to open when "any update" has apply to the ticket. So when we put ticket on hold for customer response and the ticket are waiting for an update, any kind of update. But it a hit and miss process because sometime when customer put in out of office reply which trigger the response to the email and open the ticket as soon I put it on hold, however, most of the time it was successful when customer did response. Hope this helps. Aaron

Apologises for coming late to this post but I want to confirm that we are already aware and used this process of to change the status from normal to impacted and we would actually prefer it would not be locked down to role only. It helps us greatly as well for customer to see that the service had become impacted, This would "sent the message" that something had happened to the service and we are working on the issue to fix it asap. Aaron

+1 very useful for us too and similar case scenario as Will J Douglas. Aaron