I guess they are using JIRA for planning their sprints.
Atlassian: We estimate the rebuilding effort to last for up to 2 more weeks
31–40 of 260 posts
Re: Atlassian: We estimate the rebuilding effort to last for up to 2 more weeks
#322-weeks is one hell of a Recovery-Time-Objective.
Don't complain, you'll get a few months worth of free credits or something.
Re: Atlassian: We estimate the rebuilding effort to last for up to 2 more weeks
#33Earlier quoted context omitted.
Supposedly they’re having to basically restore everyone from backups because a system designed to delete old data was a bit more efficient than it should have been: https://reddit.com/r/sysadmin/comments/u14qqq/_/i4a0mk8/?con...
Reminder: never delete data for real as your first step. Always mark it deleted along with a time stamp saying when. Then you can hide deleted itemsfrom everything. When a maintenance script goes haywire you can fix the problem quickly. Have a daily job that really deletes records marked deleted after 30 days. If that is too complicated to retrofit then have any mass cleanup script move the records to a CSV file or t…
Works until you get a bug in the deletion job. I've seen exactly this happen.
Re: Atlassian: We estimate the rebuilding effort to last for up to 2 more weeks
#34I'm honestly surprised their stock hasn't plummeted yet. There is no way I could ever invest in a company that was this terrible.
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
#35Earlier quoted context omitted.
To be fair, Jira screams SaaS. I don't want any of my company trapped on it, but if they were I'm sure as well not going to self host that spawn of hell.
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 that has dozens and dozens of projects, and somehow have people figure out which ones are where. or one really, really ugly night to cut it all over, and hope it goes well.
I'm looking for alternatives, but our team is so invested in some very, very customized workflows, its going to be a pain.
Re: Atlassian: We estimate the rebuilding effort to last for up to 2 more weeks
#36Earlier quoted context omitted.
People are more forgiving torwards themselves and their own folks, I can understand that. I'm just thinking it's important to make decisions based on facts. Some self-hosters walk around with this "my own basement is safer than Amazon datacenters" attitude and that's just not true (in most cases, I guess :D).
No. The basic assumption is only, that if I pay somebody money for the service and to keep things running, then sudden data loss is unacceptable (and a multi week downtime even more so). Some companies cannot operate effectively without atlassian products, so a fuckup of that scale might just have legal consequences depending on whom it hits.
> Some companies cannot operate effectively without atlassian products
Kind of their problem to be frank.
> so a fuckup of that scale might just have legal consequences depending on whom it hits.
Any contract those companies signed would have a cap on the retributions by Atlassian for trashing SLA targets
Re: Atlassian: We estimate the rebuilding effort to last for up to 2 more weeks
#37My company is in the middle of a multi year transition from selfhosting atlassian products to using their cloud offerings, and I am sure the infrastructure team/management is very thrilled to see this news.
While our tenant was unaffected, i told my management of this issue. They just shrugged and said we could watch and eat popcorn. I was half way expecting them to raise eyebrows
I was kinda like....."not really the point of bringing it up."
Its worth noting we have had them just delete things within our account before. In fact one of our Senior VP's had their account just....disappear one day. We couldn't @ them in chats, tickets etc. Atlassian just shrugged and "restored" the account and said it was some issue with a stored proc on their backend or something.
I have always felt uneasy about how flippant they are in their processes. But it seems that is not shared.
Re: Atlassian: We estimate the rebuilding effort to last for up to 2 more weeks
#38We'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.
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 up to 2 more weeks
#39Earlier quoted context omitted.
Supposedly they’re having to basically restore everyone from backups because a system designed to delete old data was a bit more efficient than it should have been: https://reddit.com/r/sysadmin/comments/u14qqq/_/i4a0mk8/?con...
Reminder: never delete data for real as your first step. Always mark it deleted along with a time stamp saying when. Then you can hide deleted itemsfrom everything. When a maintenance script goes haywire you can fix the problem quickly. Have a daily job that really deletes records marked deleted after 30 days. If that is too complicated to retrofit then have any mass cleanup script move the records to a CSV file or t…
How does that work around GDPR and other "Right to be forgotten" legislation? Aren't we required to hard-delete this kind of data?
Re: Atlassian: We estimate the rebuilding effort to last for up to 2 more weeks
#40Earlier 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?
https://linear.app is pretty great