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.
No post body was provided.
Atlassian: We estimate the rebuilding effort to last for up to 2 more weeks
51–60 of 260 posts
Re: Atlassian: We estimate the rebuilding effort to last for up to 2 more weeks
#52It's funny that they recently killed self-hosted Jira. If you'd self-hosted you'd be fine.
I worked at a company that self hosted Jira, and it was miserable then, I can’t imagine depending on the cloud. I’ll never approve Atlassian products after that experience.
How many tickets do you have in your non-Jira ticketing system? I count 100 tickets per person per year.
Re: Atlassian: We estimate the rebuilding effort to last for up to 2 more weeks
#53Earlier 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…
How does that work around GDPR and other "Right to be forgotten" legislation? Aren't we required to hard-delete this kind of data?
What is hard deletion? You can restore rows from database files before vacuum runs. You can often restore data from disk sectors. Some people say SSD can remap sectors under your chair and you won't even know that your deleted data is there.
Re: Atlassian: We estimate the rebuilding effort to last for up to 2 more weeks
#54It's funny that they recently killed self-hosted Jira. If you'd self-hosted you'd be fine.
> If you'd self-hosted you'd be fine.
Maybe. But you're counting on your sysadmin(s), who are also managing dozens of other things, to keep up to speed on Jira and its quirks, and apply patches and new versions as they become available without missing any steps or screwing something up.
On average, you're still probably better off having a company that knows the product also host it for you, but obviously they can make mistakes too, and the downside is that when they do it might affect all clients, not just one.
Re: Atlassian: We estimate the rebuilding effort to last for up to 2 more weeks
#55[deleted]
Re: Atlassian: We estimate the rebuilding effort to last for up to 2 more weeks
#56We'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.
[deleted]
Re: Atlassian: We estimate the rebuilding effort to last for up to 2 more weeks
#57Earlier 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
Free until the end of the year if you get in touch with them - https://twitter.com/karrisaarinen/status/1513574249121812482
Re: Atlassian: We estimate the rebuilding effort to last for up to 2 more weeks
#58Earlier 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…
> or bad SQL WHERE clause Tip: Begin an SQL session with BEGIN TRANSACTION; at the end you can either COMMIT or ROLLBACK.
Bonus tip: don't even type COMMIT until after you've run a few select queries to verify the data has in fact changed how you expected it to change.
Re: Atlassian: We estimate the rebuilding effort to last for up to 2 more weeks
#59Earlier 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…
What's wrong with restoring from backups? This is one reason they exist after all. I don't think that making a mistake in delete statement is something you would do every week.
This whole debacle is Exhibit A.
They’re lucky they have a sound backup strategy in place, and that the amount of data lost is appearing to be minimal.
Re: Atlassian: We estimate the rebuilding effort to last for up to 2 more weeks
#60It's funny that they recently killed self-hosted Jira. If you'd self-hosted you'd be fine.
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 Jira sucked because it was shitty software, not because self-hosting has to suck. Mattermost and Jitsi are easy to self-host, to give two examples that are not complete shit.