News: 1680503647

  ARM Give a man a fire and he's warm for a day, but set fire to him and he's warm for the rest of his life (Terry Pratchett, Jingo)

After 11 years, Atlassian customers finally get custom domains ... they don't want

(2023/04/03)


Atlassian customers' eleven-year quest for custom domains continues, with the Australian upstart's proposed solution failing to satisfy.

As The Register [1]reported in 2022, Atlassian floated the idea of custom domains for its custom apps in 2011. Yes, 2011.

The ticket for the change is called "CLOUD 6999" and has become infamous for the length of time it has remained unresolved. An unidentified wag has even made t-shirts bearing the CLOUD 6999 name.

[2]

Atlassian promised last year to sort it out some time in 2023, and in February [3]posted an update on its initial designs.

[4]

[5]

It hasn't gone down well. Atlassian's proposed solution requires "a company-branded domain name, a list of options for the 1st-level subdomain keyword, and a 2nd-level subdomain at your own choice."

Atlassian cloud admin experience chap Luke Liu explained that structure as delivering URLs such as internal.support.acme.com or people.knowledge.acme.org .

[6]

One of Atlassian's stated [7]company values is "Don't #@!% the customer." But plenty of Atlassian customers feel well and truly #@!%ed by the custom domain plan.

"The cloud roadmap specifically uses an example of 1 level," wrote one commenter on the 1,445-item thread discussing CLOUD 6999. "The team managing this seems to be completely lost and disconnected from the user base."

"People want to be able to have a custom URL of https://mysubdomain.mycompany.com/ where mysubdomain is a custom subdomain that could be anything and mycompany.com is my company's domain name," wrote another, adding "That is the sole requirement to this issue which is almost 12 years old, has over 1400 comments, 7700+ likes and 2500+ votes. So I'm really glad that you've spared the time to share your initial designs to the problem stated above."

[8]

"Forcing two levels of subdomain (with one of those being selected from a predefined list) doesn't make sense to me," wrote another commenter, who pointed out it is "inconsistent with pretty much every other cloud service I've used."

"If we're limited to a series of predefined 'subdomain keywords' that is by no means a 'custom domain'," wrote another.

Others are voting with their feet.

"We have decided to migrate from Jira. Good luck, Atlassian!" one customer posted in March.

"Are Atlassian executives aware that this issue is doing serious and lasting damage to their reputation?" asked another?

[9]Dead people could be designated authors of Atlassian Confluence docs and that can't be changed

[10]Developers: What if someone said you’d never have to meet with marketing again?

[11]'Private cloud server' Jira upgraded for wider teams, dragged into culture wars

[12]Atlassian to dump 500 – by email – in the name of 'rebalancing'

Perhaps not: they're currently busy [13]"rebalancing" the company by letting go of 500 people.

Do you know of a feature request older than CLOUD 6999, or Atlassian's [14]16-year-old issue that prevents changing the named author of Confluence documents? If so, [15]feel free to send me an email so we can highlight more instances of – ahem – excellent and responsive customer service from the software industry. ®

Get our [16]Tech Resources



[1] https://www.theregister.com/2022/08/12/atlassian_cloud_6999_2023/

[2] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=2&c=2ZCqjv0gr2Q3p6INlN08zAgAAAEg&t=ct%3Dns%26unitnum%3D2%26raptor%3Dcondor%26pos%3Dtop%26test%3D0

[3] https://community.atlassian.com/t5/Enterprise-articles/Custom-Domains-in-Cloud-Development-Update/ba-p/2283483?utm_source=dm&utm_medium=unpaid-social&utm_campaign=P:online*O:community*I:social_share*

[4] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44ZCqjv0gr2Q3p6INlN08zAgAAAEg&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0

[5] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33ZCqjv0gr2Q3p6INlN08zAgAAAEg&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0

[6] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44ZCqjv0gr2Q3p6INlN08zAgAAAEg&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0

[7] https://www.atlassian.com/company/values

[8] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33ZCqjv0gr2Q3p6INlN08zAgAAAEg&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0

[9] https://www.theregister.com/2022/09/06/atlassian_confluence_feature_request_confcloud_7247/

[10] https://www.theregister.com/2023/01/25/atlassian_extends_automation_to_confluence/

[11] https://www.theregister.com/2023/02/13/jira_upgrade_congress/

[12] https://www.theregister.com/2023/03/07/atlassian_fires_500/

[13] https://www.theregister.com/2023/03/07/atlassian_fires_500/

[14] https://www.theregister.com/2022/09/06/atlassian_confluence_feature_request_confcloud_7247/

[15] mailto:ssharwood@sitpub.com

[16] https://whitepapers.theregister.com/



lostinspace

It's hardly a crisis. Plenty of cloud services don't allow rebranding with your own domain name. Try getting your own domain name for Google docs, office 365 etc and let me know how that goes.

david 12

Try getting your own domain name for Google docs,

Our google docks, like our google mail, are hosted on a google domain, and that's the only way to edit them, but the public URL, like our public mail address and our login URL, use our own domain name. If you want to download or view our suppliers list from google docs. the URL in the link is ourcompany.com

ComputerSays_noAbsolutelyNo

So what is it they're selling? A product/service or being part of a brand? Both? Both, mandatorily?

That would be akin to a landlord demanding all the walls in a flat being painted brown while the tenant is renting the flat.

ChoHag

> "Are Atlassian executives aware that this issue is doing serious and lasting damage to their reputation?" asked another?

The state of Atlassian's reputation has no impact on anything at all, or else how do they continue to exist?

Have some sympathy

dogcatcher

Neither computers nor customer service had been invented when we shipped the first boatloads down-under.

THE "FUN WITH USENET" MANIFESTO
Very little happens on Usenet without some sort of response from some other
reader. Fun With Usenet postings are no exception. Since there are some who
might question the rationale of some of the excerpts included therein, I have
written up a list of guidelines that sum up the philosophy behind these
postings.

One. I never cut out words in the middle of a quote without a VERY
good reason, and I never cut them out without including ellipses. For
instance, "I am not a goob" might become "I am ... a goob", but that's too
mundane to bother with. "I'm flame proof" might (and has) become
"I'm ...a... p...oof" but that's REALLY stretching it.

Two. If I cut words off the beginning or end of a quote, I don't
put ellipses, but neither do I capitalize something that wasn't capitalized
before the cut. "I don't think that the Church of Ubizmo is a wonderful
place" would turn into "the Church of Ubizmo is a wonderful place". Imagine
the posting as a tape-recording of the poster's thoughts. If I can set
up the quote via fast-forwarding and stopping the tape, and without splicing,
I don't put ellipses in. And by the way, I love using this mechanism for
turning things around. If you think something stinks, say so - don't say you
don't think it's wonderful. ...
-- D. J. McCarthy (dmccart@cadape.UUCP)