Customers of Atlassian's hosted SaaS service OnDemand (Jira/Confluence) have been waiting 3 years for basic CNAME support. (ie: wiki.companyname.com instead of accountname.atlassian.net)
Basically asking for the ability to turn auto-play off when embedding videos into their wiki product, which seems fair enough because they really hyped their wiki's multimedia power back then.
Ticket opened November 2007, got a bunch of comments and votes, finally fixed in March 2011. Or was it? From August 2011: "This issue shouldn't be closed. I still get this issue in numerous web browsers.", with a follow up in October suggesting it was still broken. No comment from Atlassian, of course.
Whatever else you want to say about Atlassian, their development process is glacial, and their customer communications are very lackluster. It's like a tar pit where good projects go to get preserved in amber.
Can you point me to another company with a public bug tracker that you would reference as the gold standard?
Whilst I know we can always improve (and we always try to), we always end up with some bug that has been open for 5+ years that has the most votes. By definition.
At least with Atlassian you can see the bugs, vote on them, provide comments. If there is another company with this level of transparency that does it better - I'll get in contact to find out how.
Customers of Atlassian's hosted SaaS service OnDemand (Jira/Confluence) have been waiting 3 years for basic CNAME support. (ie: wiki.companyname.com instead of accountname.atlassian.net)
https://jira.atlassian.com/browse/AOD-6999
Even though it is the most voted for issue, by a factor of three it was closed last week as WONT-FIX.
Shameful - pages upon pages of enterprise customers given the royal f-u.