Thanks very much. 
Was just in the middle of a long wiki post and have lost the whole thing due to your outage, and this isn't the first time so is getting quite irritating. 
 
Why do you insist on only publishing your outages on your blog and on twitter? We don't follow your blog and twitter posts are so easy to miss. 
At the minimum we should get an email a few days in advance so we can plan and there should be a system message shortly before the outage occurs to remind people to save their work. 
 
This is a paid for service, be nicer to your customers. 
 
Annoyed (not for the first time) of London. 
 

Hi Andy, 
thanks for your response. Apologies for my rant but it was early in the morning! 
I have emailed you with some more intelligent and informed comment. 
 
I do think some more thought needs to be put into service outage announcements - the black bar is good but is not always noticeable, particularly when you always scroll straight to the bottom of the screen (maybe put it at the top and bottom?). 
Putting it on the blog and twitter is ok but not very effective, especially when we only see the announcements towards the end of the previous day (Uk time). 
 
I think some kind of opt in email service is definitely a good idea.

We are having issues with the new Ticket permissions. Our clients having access as watchers on the Support module are now unable to see all tickets they posted. IF they click on the Following option, they can see the tickets but when clicking on them it goes to a "Ticket does not exist" error.

To keep cutomers informed about our downtimes we serve a maintenance calendar which is updated regularly showing all past and future downtimes. Customers may subscribe to that calendar, sync their projects schedules and more. And that way you never again mix up downtimes coming from a different time zone like UTC, CET or whatever. That would help us in assembla, too!