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

Atlassian customers' eleven-year quest for custom domains continues, with the Australian upstart's proposed solution failing to satisfy. As The Register 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 …

[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.

[Mike 137]

Contracts

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

I rented a flat once with restrictions like that - the landlord did the decorations (ghastly geometric wallpaper) and I had to get permission to put up a picture on the wall.

[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?

[Anonymous Coward]

Damaging their reputation doesn't mean they will automatically cease to exist.

What a stupid statement. Do you always think in binary?

Besides, the article said they just sacked 500 staff......

[Anonymous Coward]

whoosh

[Anonymous Coward]

Ok, spill the beans please.

[Anonymous Coward]

Explain?

[dogcatcher]

Have some sympathy

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

[Yet Another Anonymous coward]

Re: Have some sympathy

Also have you seen the bugs there? I wouldn't want to handle them

[that one in the corner]

Re: Have some sympathy

In Australia, the bugs have you.

[Someone Else]

I dunno...

We've had the URL for our Jira installation as jira.companyname.com for quite some time, both when we hosted it locally, and when we hosted it on AWS iron. What am I missing here?

[Anonymous Coward]

Re: I dunno...

Sounds like you’re not using their cloud/hosted offering?

[sten2012]

Re: I dunno...

Aren't they imminently ending support all the self hosted options?

[P_Jamez]

Re: I dunno...

On prem yes, but hosted in a customer selected data centre is what they are pushing customers to migrate to in that case, with the Jira Cloud version (with hosting completely controlled by Atlassian) what the article refers to.

[AndyMulhearn]

Oldest ticket

The oldest one I've interacted with is this one - https://jira.atlassian.com/browse/JRASERVER-42158 which was raised on 20th Feb 2015. Rejected by Atlassian but still going strong for feedback...

[Anonymous Coward]

Re: Oldest ticket

For me it's JRACLOUD-80472. When they rolled out next-gen/team managed projects, they neglected to provide a way to set the default to private. So if you want to give, say, project managers the rights to create new projects, it's all too easy for them to provide more access than intended. What's worse is that they changed the status to say it wasn't a priority and they aren't working on it.

[AndyMulhearn]

Re: Oldest ticket

changed the status to say it wasn't a priority and they aren't working on it.

The default response to stuff they don’t care about.

[P_Jamez]

Re: Oldest ticket

It is such a pain, we have 3rd parties working in our Jira Cloud instance, had to disable next gen projects because it was too easy to share it with every one.

[Simian Surprise]

Re: Oldest ticket

https://jira.atlassian.com/browse/JRASERVER-62554 is one I've been waiting on for years (2017): there's a "current time" field if you hover over a user's name, but it's always your timezone, very useful.

[Mike 137]

"Don't #@!% the customer."

Depending on what the '#@!%' means, it might cover the proposed offering ('help' maybe?).

[Anonymous Coward]

Re: "Don't #@!% the customer."

Well, "help" *is* a four letter word.

[cjcox]

Funny in a dark way

I think it's humorous when people "threaten" (don't get to riled up about the word) leaving Atlassian.

It's got its hook in you good, you're not leaving. They could kill all your puppy friends and you will still never leave.

And they know it.

[RichardBarrell]

Re: Funny in a dark way

I worked in a company that changed ticketing systems somewhere and 4 to 6 times while I was there. I think it was only 4 but I lost count.

Switching isn't impossible. You either a) migrate your tickets over or b) lose them all, call it a temporary ticket amnesty, and then invite everyone to re file the tickets they care about most.

[Anonymous Coward]

10 years at Plesk

The Plesk community has been waiting over 10 years for multiple backup rules, such as being able to backup more than once per day

https://plesk.uservoice.com/forums/184549-feature-suggestions/suggestions/3703858-multiple-backup-rules-or-more-options

[Steve Channell]

mod_rewrite?

Surely if you want jira.xyzcompany.com you can do it with a mod rewrite rule for xyzcompany.atlassian.net.. you could even give it another name like issues.xyzcompany.com and enable migration if you want to use something else

[Anonymous Coward]

Re: mod_rewrite?

In 2023 we use Nginx not apache, but also we shouldn't have to take the load on our own systems for something Atlassian should be doing themselves. It's just unnecessary

[Mr Dogshit]

Ah say what now?

I have no idea what any of this means.

[TimMaher]

Re: “No idea”

Nor does Atlassian so it seems.

[Thorsten]

Still waiting for shared components...

Components that are shared between projects: It's been asked for time and again, at least since 2002: JRASERVER-1072, JRASERVER-12241, ...

The answer was always the same: Won't Do. Because the manual process of recreating & linking tickets apparently is sufficient for Atlassian.