8 ms·
I wonder how tense things are over at Atlassian right now. Jira seems so universally hated that it feels like any competition that ticks a few basic needs could
by tyingq 5y ago
I wonder how tense things are over at Atlassian right now. Jira seems so universally hated that it feels like any competition that ticks a few basic needs could start hurting them.
- bovermyer 5y agoProbably not that tense. A lot of enterprises with Very Big Licenses are hard-locked into Atlassian products with little to no chance of changing.
- addicted 5y agoI suspect that Azure Dev Ops is more comparable to Jira and is their real MS competition.
- ErrantX 5y agoSo, yeh I partly agree. However those orgs often have a Very Big License for GitHub Enterprise, and therefore with some enterprise porting tools it's not that high friction a switch (supplier managers will be all in favour; one less contract to manage!)
- robinhood 5y agoThey mostly don't. Once you have Jira, you have Confluence, then Bitbucket. That many less contracts to manage.
- foobarbazetc 5y agoYeah. We used to pay for GH Enterprise and run Jira/Confluence/Bamboo/etc/etc. Then we switched to BitBucket Server because it integrates better and cost a lot less, plus GH Enterprise was a weird black box VM back then that we had to hack into to make work for whatever reason. I couldn't point you to anyone who likes BitBucket Server, but as long as you're on the CLI and don't have to use the terrible web UI too much, it sort of works.
- deleted 5y ago[deleted]
- ErrantX 5y agoHard to be sure either way, but most of the sources I could find indicate this isn't true. E.g. https://www.slintel.com/tech/source-code-management/github-vs-bitbucket https://www.slintel.com/tech/source-code-management/github-v...
- foobarbazetc 5y agoThe problem is once you connect Jira to Confluence to Team Calendars to Crowd to BitBucket Server you're very deep into the lock-in. Nobody has either the time or the will to switch because, while all the software kind of sucks, it doesn't suck enough to the point where someone is going to stop working on their product and/or service to jettison Atlassian from their org.
- vinceguidry 5y agoNot so much. If the company is large enough then some teams will have enough clout to break away. Our company is mostly Jira / Confluence / Bitbucket, but our team uses GitHub SCM/Issues/Actions now. Since we've led the charge other teams are starting to migrate as well. I have a lot of awful things to say about GitHub Actions but it's probably the best fit for our team.
- formerly_proven 5y agoI was actually surprised how shallow and poorly functioning the integrations between JIRA / BitBucket / Bamboo and so on are. It all seems very basic compared to the default in OSS. In retrospect it's obvious that all of Atlassians products have been developed by separate teams / bought up and someone spent the bare minimum making each of them talk to each other.
- foobarbazetc 5y agoYou would think this -- then you look at their balance sheet and re-evaluate everything you think about software.
- robinhood 5y agoMost big corporations won't switch away from Jira and Atlassian in general anytime soon. If any changes would need to happen, it would take years.
- deleted 5y ago[deleted]
- JamesSwift 5y agoI dont see this new feature as a threat to Jira. For some tech-focused companies, sure it might make sense that everyone is in Github as their overarching project management. For all the other "regular" businesses, Jira is a more 'party neutral' solution.
- sergiotapia 5y agoJIRA is going to be fine. You think their customers are the engineers who use the tool daily, but they are not. Their customers are the managers and bean-counters that track metrics and numbers at a macro. Their tool helps those roles mostly. I hate JIRA but there is very little else serving these customers.
- whatever_dude 5y agoThere's already a dozen great competitors for Jira. Jira has a gigantic moat. Too many people - non devs mostly - are invested on it. While this new product is not negligible since it comes from a service people are likely already using, I'm sure Atlassian isn't scared in any special way.
- tyingq 5y agoYes, but the moat has a lot to do with integrated products. This would be a step that way for Github.
- denimnerd42 5y agofirst step of any agile transformation is to get yourself neck deep into atlassian products. 2nd step is to setup complex JIRA workflows and reporting and use it to break all agile principles. third step is for your devs to take none of this seriously and put fake data into JIRA which your middle managers never catch onto. then your engineers who actually want to get shit done leave and you're left only with people who put fake shit into JIRA.
- justinjlynn 5y agoThis is so close to reality it really hurts - like a good The Onion article... excellent satire. Powerful tools are flexible enough to be used correctly by knowledgeable people and help people become knowledgeable. Badly designed tools are tools which don't help people become knowledgeable and don't prevent unknowledgeable people from harming themselves or others using them. Atlassian tools, like JIRA, are almost always powerful and flexible -- capable of great good in the hands of knowledgeable people. However, they are not well designed tools, and so - the vast majority of JIRA installations and setups are just as broken as the orgs which install them and JIRA offers absolutely zero assistance or resistance to that brokenness.
- denimnerd42 5y agoRight, it turns into a political game instead of a powerful and useful tool. We have no control over how we use JIRA. It's all prescribed by someone and we don't even know who or how to reach out to them. Even the middle managers don't know how JIRA is being prescribed. They go one step worse and make Tableau dashboards from JIRA to track their own metrics that are so bad it's just... like The Office. We play the game though every day and get great feedback. This feedback is never from our customers (internal) though. Although they give us great feedback as part of the game too. Our actual delivery is very inefficient and slow though. The hierarchical structure of the org is such that feedback never makes it up the chain because that's highly discouraged. So they just keep wasting money.
- justinjlynn 5y ago
- mbesto 5y ago> Jira seems so universally hated that it feels like any competition that ticks a few basic needs could start hurting them. I regularly meet with tech companies in the 2~10 person dev team range and easily 70%+ still use Jira. These co's have the choice of choosing Jira (i.e. it isn't being jammed down on them by a corporate overlord) yet there's still hate? I don't get it. I'm beginning to think the Jira hate is simply an echo chamber about perceived overhead of project management by IC (mostly engineers), not Jira the actual product. Yes, Jira is complex, but it doesn't have to be. Most dev teams I know just need a tool to organize task intake and allocation. And most smaller ones use Jira because in most cases it'll come batteries included for a dev team. PS - according to their financials, Atlassian is doing just fine: https://www.cnbc.com/quotes/TEAM?tab=financials https://www.cnbc.com/quotes/TEAM?tab=financials
- thebooktocome 5y agoI work at a 2~20 person shop and other than the BigPicture Gantt chart plugin not scaling well, we're all more or less happy with Jira. There was a lot more complaining during our self-hosted GitLab days but I can't recall a specific reason why.
- t3e 5y agoThis aligns with my experience talking to lots of small startups of this size. It amazes me that 2-man shops use Jira, but they do, because they know it from their previous jobs and don't want to bother finding/learning a new thing. We also run across Trello and Asana a lot.
- rileytg 5y agoI use Jira with 300+ users for both software and non software projects. I don't love it for either but I don't hate it enough to move. Any tool that offered 1:1 feature parity and a full migration, would only need something as simple as slightly cheaper or faster for me to move. IMO the administration is a pain even for simple things. I've also been on Jira for at least 4 years now and the development is just sad... New UI stuff wasn't "better" just different. Pages are still slow if not slower. Reporting is abysmal; we use the API to pull pretty much all data into a database and report from that. The one tool our team's universally loved was canned– a browser extension that allowed you to screenshot and open ticket with things like browser info and URL already in the ticket. We even tried to modify the extension to put metadata from within our application (didn't work and product was sunset anyway). My outlook is that developers will move towards something like Jetbrain's issue product or maybe even GitHub issues someday. Support teams will move towards a more dedicated support style system like zendesk or a custom solution around twilio. And for non dev projects, I hope better tools come up... Microsoft project seems to still be a leader in my industry, and also seems to be universally hated amongst my teams.
- whalesalad 5y agoThey're doing their best job slowly killing Trello.
- SkyPuncher 5y agoFor day-to-day, Jira is completely fine. I get frustrated with it when I need to dive into basic admin tasks - like spinning up a new project or board. Their admin and setting panels are completely incomprehensible. Also, Jira doesn't have a story for archiving tickets. Only a straight, permanent, hard delete with no recovery. I got reminded of this the hard way. ----- We're currently switching to Clubhouse (though a completely unrelated thing was the forcing function). It comes with it's rough edges as well, but it's simple enough we can comprehend it within out headspace.
- handrous 5y agoIt's way too heavy, even for the day-to-day. A tool of that sort, for which I have to close tabs when not actively in use to save resources, even on powerful machines, or where clicking a link to a ticket might take more than very-low-hundreds of milliseconds to load, is bad. GH issues? I click a link without thinking twice, and it's open fast. Almost every interaction is quick. I can leave a dozen tabs with GH issues open for weeks and not notice. Jira? Asana? "Ugh, a list of five issue links and I don't know which I need... fuuuuuck I don't want to open all these to find the right one, should take 10s total but will take a minute or so", and "why's my whole system feel weird? Damnit, I left Jira/Asana open again, didn't I?"
- ohyeshedid 5y ago> It's way too heavy It's basically the CPanel of ticket systems.
- waylandsmithers 5y agoSame. My personal pet peeve is "workflows", aka, you moved something from To Do to In Progress, and now it's impossible to move back because its not part of one of the allowable paths for a ticket. It's just like... why. PMs spend all this time designing the workflows only to make more work for themselves when everyone needs them to manually move things.
- ec109685 5y agoJira’s mobile interface is dreadful. Most features are missing and basic things like state survive a round trip through an sso flow are missing. They obviously lack any sort of customer obsession to let this persist.
- tshaddox 5y agoI always got the sense that Jira is only universally hated by people who use it but have absolutely no say in whether they have to use it.
- louisvgchi 5y agoHaving no say in having to use any piece of software is a straightforward way to make people hate it.
- ATsch 5y agoI don't think that will happen just because the real problem is how software like this is usually bought. They'll ask 20 departments for their (heavily conflicting) requirements and then chose the one that ticks the most boxes without paying any attention to usability, which automatically means jira. To compete with that you'd have to do the same thing as them, at which point your tool end up just as unusable. (also see: gitlab)
- deleted 5y ago[deleted]
- cuddlybacon 5y agoI bet they aren't too worried. This seems like a product area where hitting all the features on a purchasing manager's feature list is more important than being good. Atlassian seems optimized for that.
- jjcm 5y agoEx-Atlassian here. Last day was around a month ago. Not tense at all. You'd be surprised at how many people actually like Jira, mainly because of how customizable it is. That in my opinion is it's biggest boon and its greatest curse. Every Jira instance is so different it's hard to compare between them. Stock isn't bad at all and works quite well. There are performance issues for sure, but I've yet to see a competitor that has the level of complexity Jira provides do so at a significantly faster speed. For what it's worth, culture wise Atlassian was great because of how not tense things were. A lot of that is the Australian values in the company. It's very much work-to-live rather than the live-to-work of most Bay Area companies.
- Dunedan 5y ago> You'd be surprised at how many people actually like Jira, mainly because of how customizable it is. Are there any numbers of how many of the users like it, compared to how many users struggle with it? I can't imagine that a majority of Jira users likes it, as that's not my experience. I have met very few people (mainly project managers) so far, which believe that Jira (and other Atlassian products as well) are great products.
- beebob 5y agoI have to say that I strongly believe that the hate for Jira doesn't come from Jira but from misconfigured workflows. I used to use a stock Jira in my last companies and never understood what people were complaining about. I had boards with the simplified workflow and the team had free reign. I first started being annoyed by it when I joined a large corporation with a central department that would enforce specific workflows and processes. Now I can't move tasks into a sprint without assigning them to a person first, can't move task from status x to y and have a 100 custom fields in there. It's no fun anymore. At the same time the projects are owned by project management and it doesn't feel like home anymore. Where I initially opened up my Jira Board first thing every morning it now has become a chore. At the same time I have to say that I kinda understand where those processes come from. I now work in an industry where accidentally using a wrong issue type or forgetting to assign issues to specific code changes can become an actual issue due to traceability requirements mandated by law.
- MikusR 5y agoThey are so not bothered that they have started to "enterprise" Trello