81–90 of 772 posts
Earlier quoted context omitted.
I can't believe that they would intermix the data in that way... but if they did, godspeed to them, they're likely still overpromising what can be done in this time frame.
How else do you run a multitenancy platform?
Earlier quoted context omitted.
I can't believe that they would intermix the data in that way... but if they did, godspeed to them, they're likely still overpromising what can be done in this time frame.
How else do you run a multitenancy platform?
> Most of them said they won’t leave the Atlassian stack, as long as they don’t lose data. This is because moving is complex and they don’t see a move would mitigate a risk of a cloud provider going down. I still don't understand the strangehold JIRA has on some clients. I can't quickly think of another SaaS product that could be down for almost 2 weeks and not have most customers leave.
But it's got what plant's crave...
Earlier quoted context omitted.
I would really like to understand who makes the decision to purchase JIRA. It's like the C++ of ticketing software--it does everything because no one wanted to sit down and think critically about the use cases and instead decided it would be easier to say "yes" to every single feature request. It definitely feels like whoever is buying JIRA is not on the team who is using it (maybe IT or finance) because it ticks the…
ime people pick Jira because they've used Jira and have been promoted via the peter principle to the level at which they make purchasing decisions.
prevents data integrity issues in relational databases, makes debugging easier and prevents disasters.
ideally also include a timestamp, both for bookkeeping and safe tools that only remove things that have been soft deleted for some time and are safe to delete without compromising integrity of anything that is not deleted (this is especially important in relational data models)
Earlier quoted context omitted.
> Faulty script. Second, the script we used provided both the "mark for deletion" capability used in normal day-to-day operations (where recoverability is desirable), and the "permanently delete" capability that is required to permanently remove data when required for compliance reasons. The script was executed with the wrong execution mode and the wrong list of IDs. The result was that sites for approximately 400 cu…
I suppose that’s why you don’t combine a tazer and gun into 1 device with 2 triggers.
Earlier quoted context omitted.
How else do you run a multitenancy platform?
This. It would be an impossible nightmare for every account to have their own DB. Hundreds of thousands of accounts and databases....
Would still be some maintenance, don't get me wrong. But far from impossible.
so this is the end of Atlassian as a company right?
Earlier quoted context omitted.
I would really like to understand who makes the decision to purchase JIRA. It's like the C++ of ticketing software--it does everything because no one wanted to sit down and think critically about the use cases and instead decided it would be easier to say "yes" to every single feature request. It definitely feels like whoever is buying JIRA is not on the team who is using it (maybe IT or finance) because it ticks the…
What's wrong with C++? Seems unfair to compare it with JIRA.
> it takes between 4 and 5 elapsed days to hand a site back to a customer. Atlassian's SLA page says, Premium Cloud Products 99.9% That's 43 minutes of downtime per month. That works out to, Atlassian can't have any more downtime for the next 14 years. Are SLAs even real? I'm being slightly facetious. From the page text it's just a threshold after which I think you're entitled to some money back for that month.
And a couple of percent discount on services for the extra downtime isn't really a meaningful consequence.