After 11 years, Atlassian prospects lastly get customized domains … they do not need

Atlassian prospects’ eleven-year quest for customized domains continues, with the Australian upstart’s proposed answer failing to fulfill.

As The Register reported in 2022, Atlassian floated the concept of customized domains for its customized apps in 2011. Sure, 2011.

The ticket for the change known as “CLOUD 6999” and has turn into notorious for the size of time it has remained unresolved. An unidentified wag has even made t-shirts bearing the CLOUD 6999 identify.

Atlassian promised final yr to type it out a while in 2023, and in February posted an replace on its preliminary designs.

It hasn’t gone down effectively. Atlassian’s proposed answer requires “a company-branded area identify, a listing of choices for the 1st-level subdomain key phrase, and a 2nd-level subdomain at your individual selection.”

Atlassian cloud admin expertise chap Luke Liu defined that construction as delivering URLs corresponding to inside.help.acme.com or individuals.data.acme.org.

One in every of Atlassian’s acknowledged firm values is “Do not #@!% the shopper.” However loads of Atlassian prospects really feel effectively and really #@!%ed by the customized area plan.

“The cloud roadmap particularly makes use of an instance of 1 stage,” wrote one commenter on the 1,445-item thread discussing CLOUD 6999. “The workforce managing this appears to be fully misplaced and disconnected from the consumer base.”

“Folks need to have the ability to have a customized URL of https://mysubdomain.mycompany.com/ the place mysubdomain is a customized subdomain that might be something and mycompany.com is my firm’s area identify,” wrote one other, including “That’s the sole requirement to this problem which is sort of 12 years outdated, has over 1400 feedback, 7700+ likes and 2500+ votes. So I am actually glad that you’ve got spared the time to share your preliminary designs to the issue acknowledged above.”

“Forcing two ranges of subdomain (with a kind of being chosen from a predefined checklist) would not make sense to me,” wrote one other commenter, who identified it’s “inconsistent with just about each different cloud service I’ve used.”

“If we’re restricted to a sequence of predefined ‘subdomain key phrases’ that’s not at all a ‘customized area’,” wrote one other.

Others are voting with their ft.

“We’ve determined emigrate from Jira. Good luck, Atlassian!” one buyer posted in March.

“Are Atlassian executives conscious that this problem is doing severe and lasting harm to their repute?” requested one other?

Maybe not: they’re at present busy “rebalancing” the corporate by letting go of 500 individuals.

Have you learnt of a function request older than CLOUD 6999, or Atlassian’s 16-year-old problem that forestalls altering the named writer of Confluence paperwork? In that case, be at liberty to ship me an e mail so we will spotlight extra situations of – ahem – glorious and responsive customer support from the software program business. ®