Isn’t this the sort of thing that would normally have made it to the first page here a while ago?
Just asking, I’ve never used any of their products
Just asking, I’ve never used any of their products
They have decided to treat their customers worse than Oracle does, with nothing but threats that you can make the pain stop if you just go with cloud. They’re an absolutely despicable company.
So after enduring all this, there’s a huge amount of schadenfreude that customers are experiencing watching them be down for so long. They absolutely deserve it.
You can't self host now, just use their cloud offerings.
Upside, it’s the same code just difference license file, and it enables clustering (plus lots of other artificially limited features)
Downside, it’s a subscription license and it’s insanely expensive.
Wow...
https://architectureau.com/articles/worlds-tallest-hybrid-ti...
Hell of a bet on building more physical space with WFH and other factors making office space cheaper. Plus investing in a new building material concept. This seems like a passion project for someone high up in their food chain.
> expected to cost $546 million and be completed in 2026.
> Construction is expected to create 2500 additional jobs and generate $1 billion dollars in revenue annually.
A quote from the project page: "This project is not just about being green, it’s a whole systems approach to design, construction and habitation. It will demonstrate that change is possible and has many advantages for the planet, our cities and business."
Sounds vague.
In ranking companies by "Ugh, your product sucks" many people would put Atlassian pretty high. So if their product sucks, why would their cloud infrastructure be better?
Their software is "enterprise software", in all the bad ways. eg expensive, slow performance, doesn't work properly, products that don't seem to receive updates after their creating company was acquired (eg StatusPage), etc.
But they have a marketing/PR department, which covers over a lot of those problems.
For anyone actually trying to work with it on a daily basis is a huge pain in the ass. Mostly due to the dreadful performance, which was bed enough with the on prem solutions and has now gotten even worse on cloud. Another wtf example is their wysiwyg editor actually has no own markup, it is stored as plain html and has tons of bugs, such that things you edit will return in a different format after you press save, with no way to restore it. This is just so fundamental input form 101 that you wonder what else is equally buggy underneath, especially this being one of their main values. Every one of their product uses a different such editor, all with their own set of different bugs.
Otherwise, you can’t deny that their products are actually very powerful. If only they cared more about basic usability they could have a really good offering.
https://jira.atlassian.com/secure/WikiRendererHelpAction.jsp...
Their API was unbelievably slow but still better than having to interact with the web app. Please Oh Deities, let me be on an hourly contract the next time I have to use their products!
the latter is forgivable, the former is not.
The killer feature, the reason I’ve painfully endured JIRA for about 15 years…
It’s always cited as important but I’ve never actually seen them used in anger.
My co-worker once lost 2 hours of work spent on drafting a new JIRA issue (or maybe it was a comment, I don't remember).
There's a feature request in their tracking system for preserving un-saved work. It's been there for almost 20 years now: https://jira.atlassian.com/browse/JRASERVER-4233
Guess which one of those two they're sunsetting...
I actually like Confluence, it’s a well done wiki solution.
Good luck finding it ever again unless you know exactly what you are looking for.
You can mitigate the issues in the search if you are organise your content well but the search is still deficient in other ways.
Compared to decent project management software it has almost no project management features.
And then a point upgrade removed that support in favor of their own rich text format, so in an instant all our tooling died. We were not happy campers.
I have other thoughts about Jira: https://honeypot.net/post/jira-is-a-code-smell/
Personally I preferred the ability to edit pages as markdown, and we toyed with ways to allow users to edit the rich pages in markdown (i.e. a new transformer from the storage format to wiki-markup, instead of the editor format) - but it wasn't possible to not come up with a diverging solution for the transformations here (at the time, given the time we had spent on it).
Whilst we copped a lot of flack from the die-hard Confluence users when this was done, the vast majority of users liked the change. Also from a different angle, this was a really fun time at Atlassian - we had run out of space in the CornX (office at the time) so we had leased the floors above the pub next door (The Dundee Arms), and there were five of us in there, all with out machines crammed around a single table in this tiny room. Good times.
If you use Jira to track sprints, and you want to view the previous sprint, how would you expect to do it? I don't mean a sprint from 5 years ago, I mean the one from last week. Let's say you want to view stories that didn't get completed last sprint, or you just want to see what happened because you're doing a retrospective. How would you expect to go about this in a mature product for which your organization pays money?
You might say "well, there's probably a button on the current sprint that lets you go back in time to the last sprint. Like, some form of pagination. Or, maybe you can even set a date on a calendar and see the active sprint during that date. That would be cool."
According to Atlassian's support forum, there is "no way to currently do this"[1].
[1] https://community.atlassian.com/t5/Jira-Software-questions/H...
You can approximate it by building a custom query, or going into a reporting dashboard (if you have access). You shouldn't need to.
I’ve used JIRA in 3 companies and it was always the worst piece of software I had to interact with. Now we just use Github issues and their “Projects beta” and it’s a huge improvement. Engineer first workflow rather than optimized for creating some pseudo insightful views for useless managers
It's fine. Certainly no worse than any other wiki that just accretes content.
(Then again, we're not doing anything overly sophisticated with it, or relying on any of its features for critical workflows.)
(If there isn't that much content, now would definitely be the time to do this, so you entrench the capability and get everyone to depend on it to the extent that it must be fixed once it can't keep up. :P)
Are executives just scared of getting fired for moving off of Azure DevOps and Jira? They’re both garbage pieces of software and everyone who uses them knows it.
I’ve learned to translate “We need to buy into Atlassian’s suite” as “our process is broken and we’re blaming the tools.” This has the standard “now you have two problems” punchline. I’ve seen this play out several times at companies of varying sizes. The endgame “fix” is always that one or more people become entirely devoted to wrangling the complexities of the Atlassian stuff, but a dedicated person/team would have fixed the problem with the old tools, too.
Yeah, no.
i've definitely been using bitbucket and jira for the last four days without noticing anything wrong.