News for hackers. Stuff that matters.
Re:Atlassian: We estimate the rebuilding effort to last for ... by yabones on Monday April 11, 2022 @01:29PM (#30992094)
We're mere weeks aware from migrating to their could platform after the self-hosted rugpull. This really doesn't give me confidence in their ability to not break my stuff.
Re:Atlassian: We estimate the rebuilding effort to last for ... by justin_oaks on Monday April 11, 2022 @02:29PM (#30992730)
There are two ways this can go:

1) This outage will get their organization to prioritize work such that it never happens again.

2) This outage is representative of a dysfunctional organization that can't prioritize work correctly.

If you've been using Atlassian software for a while and are used to how they prioritize tickets then one of those options seems far more likely than the other.

Re:Atlassian: We estimate the rebuilding effort to last for ... by borplk on Monday April 11, 2022 @10:49PM (#30998015)
I can tell you #1 never happens. It will be a temporary effect of the management green lighting the years of neglected maintenance work until everybody forgets about it and it will go back to business as usual until the next incident happens and the cycle repeats.
Re:Atlassian: We estimate the rebuilding effort to last for ... by laurent92 on Monday April 11, 2022 @02:36PM (#30992820)
> 1) This outage will get their organization to prioritize work such that it never happens again

It has already happened in the past.

Re:Atlassian: We estimate the rebuilding effort to last for ... by uuyi on Monday April 11, 2022 @03:34PM (#30993636)
Re:Atlassian: We estimate the rebuilding effort to last for ... by lmc on Monday April 11, 2022 @03:46PM (#30993818)
"An Atlassian spokesperson contacted by The Reg blamed the loss on the failure of “multiple” storage disks at its cloud storage provider on 28 April."

10 years ago to the month.

So as long as everyone plans a vacation for this time in 2032 it'll be OK.

Re:Atlassian: We estimate the rebuilding effort to last for ... by justin_oaks on Monday April 11, 2022 @05:52PM (#30995595)
Ah, you mean that outages have happened in the past, not that Atlassian has changed because of an outage.
Re:Atlassian: We estimate the rebuilding effort to last for ... by uuyi on Monday April 11, 2022 @03:01PM (#30993173)
Same situation.

Absolutely no one even knew this was happening and doesn’t give a shit now because it’s a project death march.

JIRA as a whole has been a fucking shit show of a product over the last decade even on-prem.

Re:Atlassian: We estimate the rebuilding effort to last for ... by digerata on Monday April 11, 2022 @03:16PM (#30993366)
I will say that back when Bugzilla was it, JIRA rocked. It was amazing the new power you had and the functionality it provided.

We self-hostd JIRA from 2008ish to 2014ish. (memory is fading on exact dates) By the time we decided to stop using JIRA, we fracking hated JIRA and would never return.

Since then, GitHub Issues, Trello, Clubhouse (neé Shortcut) all provide less friction in day to day use. As an Enterprise, I do believe Shortcut is your best bet.

Re:Atlassian: We estimate the rebuilding effort to last for ... by cataflam on Monday April 11, 2022 @07:29PM (#30996558)
Not trying to nitpick, just for your information

> Clubhouse (neé Shortcut)

It's the opposite: Shortcut (née Clubhouse), as "née" means "born", so it's the name it had at birth, the old name

The more you know!

Re:Atlassian: We estimate the rebuilding effort to last for ... by paledot on Monday April 11, 2022 @09:50PM (#30997632)
A valuable piece of pedantry, since I hadn't heard of either name and interpreted the GP to be referring to a product now named Clubhouse.
Re:Atlassian: We estimate the rebuilding effort to last for ... by abraae on Monday April 11, 2022 @02:41PM (#30992885)
Why would you continue with that plan? You couldn't get a clearer warning signal.
Re:Atlassian: We estimate the rebuilding effort to last for ... by yabones on Monday April 11, 2022 @03:19PM (#30993415)
To be quite honest, the problem is historical. We have over a decade of project plans, support tickets, change control logs, etc in our Jira instance. There's simply no painless way to export that into another product that will have approximately the same functionality and features. There's a few that come close, but all fall short of a drop-in replacement.

The only options now are the $$$$$ "datacenter" license, migrating to the dangerously unstable cloud, or not doing anything and running unsupported EOL software.

Re:Atlassian: We estimate the rebuilding effort to last for ... by abraae on Monday April 11, 2022 @03:44PM (#30993794)
I totally understandthat. But at the same time, a multi-week outage is really a sign of an org that simply does not have their shit together at all.

But the lack of transparency is the worst. Another post speculated that Atlassian has lost data, doesn't even have backups, and is re-creating it by munging their emails and diffing them to re-create history. I can't really imagine that's tue - but what if it is, and Atlassian is concealing things?

Re:Atlassian: We estimate the rebuilding effort to last for ... by joshuaissac on Monday April 11, 2022 @05:49PM (#30995554)
> the $$$$$ "datacenter" license, migrating to the dangerously unstable cloud, or not doing anything and running unsupported EOL software

Data Center is pricier than Server, but isn't it still cheaper than Cloud? And you control your own back-ups as with Server, so Atlassian cannot lose your data.

Re:Atlassian: We estimate the rebuilding effort to last for ... by thanatos519 on Monday April 11, 2022 @03:17PM (#30993382)
"could platform" ... perfect typo!