Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Atlassian: We estimate the rebuilding effort to last for up to 2 more weeks

twitter.com

Post reply on HN
Print view View original

201–210 of 260 posts

Re: Atlassian: We estimate the rebuilding effort to last for up to 2 more weeks

#201

Post by progman32 »

davio wrote: post #116
danuker wrote: post #43

Earlier quoted context omitted.

> or bad SQL WHERE clause Tip: Begin an SQL session with BEGIN TRANSACTION; at the end you can either COMMIT or ROLLBACK.

I always liked LIMIT when doing dangerous stuff in prod

For anyone doing this, just keep in mind that chucking on a LIMIT 1 can give you a false sense of security. For example, say you want to drop a single row but forget the WHERE. A LIMIT 1 will return "yep, deleted one row" but it's not the one you wanted (instead, it's whatever row came up first). Better to do the operation in a transaction that you can rollback - that way, you can better validate the results of your operation before committing.

Re: Atlassian: We estimate the rebuilding effort to last for up to 2 more weeks

#202

Post by sitharus »

justin_oaks wrote: post #64
xenadu02 wrote: post #29

Earlier quoted context omitted.

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…

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…

If you're using MS SQL Server it natively supports temporal tables, which take care of this problem for you. There's also an extension for Postgres, and of course triggers.

Temporal tables should really be used more often.

Re: Atlassian: We estimate the rebuilding effort to last for up to 2 more weeks

#204

Post by noddingham »

senorsmile wrote: post #99
planb wrote: post #68

As the person responsible for running Jira and Confluence on premises at my employer I‘m looking forward for the next time one of their sales droids contacts me to make us move to their cloud services (despite me stating that we are not interested multiple times)…

They are discontinuing on prem after 2022 though. What is your plan if not to migrate to their SaaS offering?

End of support is February 15 2024, not 2022. But your current server licenses are perpetual so you _could_ keep running them.

Re: Atlassian: We estimate the rebuilding effort to last for up to 2 more weeks

#205

Post by radicalriddler »

aaronbrethorst wrote: post #95

The wildest part about this service outage to me is that Atlassian's stock is up 10% over the past month.

The outage has been in the past week and it's down over 10%... talking about the last months price changes is irrelevant compared to the last week.

Re: Atlassian: We estimate the rebuilding effort to last for up to 2 more weeks

#206

Post by noptd »

znpy wrote: post #162
deergomoo wrote: post #136

Earlier quoted context omitted.

> Jira Cloud is incredibly slow I haven’t used Jira Cloud in any great depth, but I did play around with it as part of trialling the free plan and was amused that you could quite easily come across warnings to backup your installation and consult your system administrator before proceeding…how exactly do I do that for a cloud service? Doesn’t exactly inspire confidence. At my last job we used Bitbucket Cloud and that…

> I haven’t used Jira Cloud in any great depth. I have. It's painfully slow. But slowness isn't really the problem, the problem is that it's unpredictable. I wait for the interface to be fully loaded, so I click on a text box and i start typing. Then FU--ING something takes the focus to some other element in the web page and now i'm typing random shortcuts (like reassigning tickets, changing status or whatever). It's…

>now i'm typing random shortcuts (like reassigning tickets, changing status or whatever).

This happens to me often and it's absolutely infuriating. I'd prefer a blocking spinning wheel of death over that nonsense. It's all but ensured that I'll be looking elsewhere when choosing project tracking software in the future.

Re: Atlassian: We estimate the rebuilding effort to last for up to 2 more weeks

#207

Post by Underphil »

kuschku wrote: post #27
media-trivial wrote: post #5

Earlier quoted context omitted.

We're using the cloud version and we're fine too (no outage). What's your point? Are you claiming that self-hosted is never down? Or that self-hosted is more reliable? Because I doubt that. Difference is just that when self-hosted goes down, it doesn't end up in the news.

My own self-hosted services have about 20 min downtime a month. I’ve never – not at any point in the past 10 years – gone over 24h of downtime. JIRA will now have 3 weeks downtime. Distributed systems have complexity that grows superlinear, which leads to more and longer incidents.

We self-host C & J for just shy of 3,000 users and haven't exceeded that.

Re: Atlassian: We estimate the rebuilding effort to last for up to 2 more weeks

#208

Post by paledot »

cataflam wrote: post #182
digerata wrote: post #69

Earlier quoted context omitted.

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…

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!

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 up to 2 more weeks

#209

Post by Throwawayaerlei »

ivanvas wrote: post #107

Looking at the company financials and timing, the wooden headquarters might have to wait. I don't envy engineers there right now, some dpts. Stay strong, don't burn out! https://architectureau.com/articles/worlds-tallest-hybrid-ti...

The "Edifice Complex" has been taken to be a bad portent for a company.

Obviously not universal, but if upper management has decided to spend a lot of time focusing on a marque building they're not focusing on the business itself.

Re: Atlassian: We estimate the rebuilding effort to last for up to 2 more weeks

#210

Post by atonse »

maclockard wrote: post #40
whiteboardr wrote: post #34

Earlier quoted context omitted.

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

Linear seems optimized for teams that just build one product at a time. We tried it and while the app was elegant, the concepts just didn't map to our mode of multiple repos and across many different clients (some product, some consulting, etc). I don't know if that changed, but that stopped us from adopting Linear.
Post reply on HN