21–30 of 205 posts
We'll likely be running on prem as long as is reasonable without support, and then moving to an alternative - maybe gitlab. Atlassian lost our business with this move.
One day the pendulum will swing back in the other direction. Until then, those of us who disagree with putting absolutely everything into the cloud will just have to sit back and bide our time.
I wonder where they actually put in the billions of dollars they've raked in from their customers - from the looks of it, definitely not in the product, and also not in support given that it's very obvious that their first line of support is some Indian guys in a callcenter with the complete inability to do more than follow a badly written script.
1. Changing default sorting order to 'most recent first'; I thought I was going insane at first when it happened
2. Making the comment box a floating page element so it always takes up about 25% screen real estate
I've been able to script these back to their old behavior but wouldn't it be nice if they added settings to toggle the behavior...
My company has been on Atlassian products for the past like 20 years so it'll be interesting to see whether we migrate to their cloud garbage or migrate off them altogether.
Earlier quoted context omitted.
I have the opposite experience; many if not most of the features have gotten faster as the features have expanded in capability
> as the features have expanded in capability Yet I still cannot import anything like in the old editor (e.g. markdown), adding images in lists was added two years after forcing switching to the new editor and you still cannot continue numbered lists in another item line and have to start over. Extensions exist to do this but these things should be standard in any editor.
The problem with Jira is that we don't have many alternatives at enterprise level. Maybe for smaller teams ( I had a lot of hopes for Github Issues [0] but since they announced the product on last year's Universe event, there were not many news. Maybe this November they will come back with an update. At this point, I feel Jira is like WordPress. It maybe slow and overbloated, but you can have absolutely any plugin an…
It is possible to do, I ack that we're below your 1k engineers threshold (though the OSS side is way above), but the problem isn't Github it's whether you (as an org) dictate a single SDLC that you enforce via a tool and as we aren't doing that and we're not yet encountering difficulties (beyond culture shock when people onboard and can't find what they're used to elsewhere, being Jira). By working with autonomy, and in fact embracing OSS and the community (meaning we can't hide info in internal Jira instances), it's easy to avoid Jira.
That's the rub though, many places do not want to give engineers autonomy like this.
but their decision to abandon on-prem has resulted in the company migrating away from all atlassian products
the best thing atlassian have ever done!
I personally they haveheld back nearly every organization I've worked for in some way or another over the last 15 years. These Atlassian products are the destroyers of enjoyment, satisfaction, project management and productivity.
Issues I've encountered with Confluence and JIRA:
* Painfully slow UI.
* The confusing UX for JIRA.
* The 100x ways to accomplish the same things in JIRA.
* The fact project managers always end up going back to a spreadsheets because JIRA doesn't cut it, even though they insist they need to continue using it.
* The way people bastardize every installation of JIRA it never seems to solve the problem it was designed to solve adequately, or because that was encouraged via "plugins".
* JIRA can't be upgraded because someone installed a plugin that cannot be upgraded too, but the whole org is dependent on some functionality from said plugin.
* The pathetic search in both product.
* The shitty editor in confluence I really cannot believe anyone is still interested in using it.
* Confluence not having support for Git or some similar version control system or pull-request like process support, making everyone to afraid to make changes to documentation.
* Confluece, errors, just blows up sometimes when I go to save a document.
I get that the plugins issues aren't entirely Atlassians fault in some ways ,but in others they are. I believe their plugin implementation allowed people to way too tightly integrate with the core product, not working like "integrations" but actually having the ability to break basic work flows. It was a huge mistake.
I personally use GH issues and projects and the simplicity of it is really fantastic, when I'm forced to go back to JIRA at work, I just feel that I cannot believe I get paid to waste time wrangling these products into doing something useful.
Earlier quoted context omitted.
> as the features have expanded in capability Yet I still cannot import anything like in the old editor (e.g. markdown), adding images in lists was added two years after forcing switching to the new editor and you still cannot continue numbered lists in another item line and have to start over. Extensions exist to do this but these things should be standard in any editor.
The new editor in Jira is drives me nuts. They replaced a perfectly good, functional markdown editor with the current POS, and it causes me problems nearly every single day.
I don't remember the last time I had a problem with an editor except for using any Atlassian product. Not sure what the fuck they do, but they really seem to have trouble with this aspect of their products. Which is ironic because their products are essentially CRUD products with a heavy emphasis on data entry.
Like, if anything out their products needs to work well, it's the editors.