So, let me get this straight: * It's been deleted for a week already, they estimate they might need two more weeks. Three in total. * They claim to have "extensive backups", and hundreds of engineers working on it. What? How? This simply doesn't go together. Why would restoring from backup take three weeks? Either their backups aren't complete, or they need new software written for the restore, or something else does…
Atlassian: We estimate the rebuilding effort to last for up to 2 more weeks
231–240 of 260 posts
Re: Atlassian: We estimate the rebuilding effort to last for up to 2 more weeks
#232Earlier quoted context omitted.
Because all the others are equally bad, basically. The options for enterprisey issue management are quite slim.
I really like ClickUp. Never had an issue.
Re: Atlassian: We estimate the rebuilding effort to last for up to 2 more weeks
#233Earlier quoted context omitted.
If technical competency had any bearing on stock prices they should've been at 0 since long ago. Their stock price is tied to the amount of clueless/shitty companies that will still cling onto their products regardless of what happens, and I don't think this incident is going to change much.
Honest question: Since Trello is part of Atlassian aswell - what are good, reliable and above all lightweight alternatives for managing projects without the “pseudo-agile” rabbit holes of functionality?
Re: Atlassian: We estimate the rebuilding effort to last for up to 2 more weeks
#234Earlier quoted context omitted.
The cloud is just someone else's servers. 3-2-1-0 Applies to all data, at all time, in all places
Normally it's 3-2-1, what does the 0 represent here? 3 copies 2 different formats (ex. HDD, cloud) 1 offsite 0 lost data? :D
That's not what "format" means, it's more like DB-Dump and DB-VM-Dump, or pure Files and VM-Dump, or something like restic-repo and rsync(pure files).
Re: Atlassian: We estimate the rebuilding effort to last for up to 2 more weeks
#235Earlier quoted context omitted.
They are discontinuing on prem after 2022 though. What is your plan if not to migrate to their SaaS offering?
What are disconnected customers going to do? Surely they won't cut off the entire US military and DoD by terminating that cash cow of on premises.
Atlassian completely ignored the large number of smaller customers who are legally forced to use an on-premise solution. If the software industry was so hell-bent on SaaS there would be a great business oppotunity in creating an on-premise Jira competitor.
Re: Atlassian: We estimate the rebuilding effort to last for up to 2 more weeks
#236Earlier quoted context omitted.
We will probably bite the sour apple (not sure if this is correct English but you’ll get the meaning even if it’s not) and switch to the data center edition which is still on prem but costs approximately twice as much.
A bit from the Boom Chicago show I saw in Amsterdam around 2004: “The Dutch expression ‘bite the sour apple’ means the same thing as ‘bite the bullet’ - Americans are obsessed with guns, and the Netherlands is full of shitty food.”
Re: Atlassian: We estimate the rebuilding effort to last for up to 2 more weeks
#237Could Atlassian be liable for damages?
Re: Atlassian: We estimate the rebuilding effort to last for up to 2 more weeks
#238Earlier quoted context omitted.
Self-hosted full Atlassian stack (jira, confluence, bamboo, bitbucket) for 6+ years. ~200k tickets. To be honest, it just runs with minimal issues. Mostly downtime is just upgrades. I can remember a few times we've had to add (JVM) memory as our usage increased. Not sure what we're going to do with the discontinuation of server product line. We self-host to keep source code, etc. more than one configuration mistake (…
We are in the same boat. We are looking at the cloud, but the migration tools are just a pain. I can migrate a project to the cloud from Jira, and it even gives me a report of workflow transitions I have to manualy update/change to fix, which is great. But then, there is no way to keep it in sync. I have to blow that project away in jira cloud, and migrate it again. So I Have to hard-cut over projects, on a system th…
I think one reason Atlassian was successful is that they always invested a lot of effort in building tools to migrate to their products from any of their competitors (obviously not the other way around).
Re: Atlassian: We estimate the rebuilding effort to last for up to 2 more weeks
#239Earlier quoted context omitted.
If technical competency had any bearing on stock prices they should've been at 0 since long ago. Their stock price is tied to the amount of clueless/shitty companies that will still cling onto their products regardless of what happens, and I don't think this incident is going to change much.
Honest question: Since Trello is part of Atlassian aswell - what are good, reliable and above all lightweight alternatives for managing projects without the “pseudo-agile” rabbit holes of functionality?
Realistically, though, you're more likely to be able to convince other project members to use the issue tracker of whatever forge they're comfortable with, for instance Gitlab, Gitea, Pagure or Sourcehut.
Re: Atlassian: We estimate the rebuilding effort to last for up to 2 more weeks
#240Earlier quoted context omitted.
I agree that data must never be "deleted and forever gone" unless you've already been very sure about it a few time. But I would like to warn people about certain implementations of database "soft deletes" that I'm not a fan of. To be clear, I'm talking about the idea of having a "deleted" and/or a "date_deleted" column and using those columns in the WHERE clause to filter out rows that shouldn't be visible. That pat…
A "deleted" field type deletion is also how you get a massive fine from a GDPR agency when they find out that you're not actually deleting PII properly.