401–410 of 539 posts
I feel like hating on Jira is the pastime that is now passed down from each generation of programmers to the next. I'm going to stick up for Jira. I certainly don't "love" Jira, though I do think they've made significant improvements with "new Jira" (I think they call them team-managed projects now). The problem I have with the incessant Jira bitching is that I rarely feel that bitchers have a true understanding for…
Earlier quoted context omitted.
The self-hosted version is discontinued and you can't buy it any more if you aren't already a customer.
Incorrect. The cheapest license version is discontinued, ”server”. Data center license is not.
“There’s only two types of people that hate JIRA: 1) those that haven’t tried any of the alternatives or 2) those that didn’t have a dedicated team to configure and maintain JIRA for them”
Earlier quoted context omitted.
Yes, we switched to Jira from a piece of abandonware (simple php based bug tracker) several years ago. Jira is kinda slow sometimes, but not horrible. And yes, like you said, once you get it configured it works great. Overall, we are very happy with Jira and it's worth the cost for the value it brings to the organization (still hurts the wallet, but it's at least justified). ...and then Atlassian comes along and rug-…
Yeah that's a bit rough. Though I think for most people the cloud solution is the way to go, though - even if it's an evil Saas-recurring-revenue play. I was close enough to a previous team that used to admin an on-prem Jira (~7 years ago) to know it wasn't just set-and-forget, and also that almost all the slowness users complained about was due to under-provisioned hardware. Honestly I reckon half of Jira's reputati…
Also no shortage of folks elsewhere in this discussion talking about cloud slowness.
We've had plenty of irritations with our on-prem, but slowness, not so much. And yeah, for us it's mostly about keeping the data internal.
Not using Jira is a red flag for me, and I won't work for any company that doesn't use Jira. The reason is, Jira is so standard at this point, if a team uses a non-Jira product, they must have an overly powerful CTO or team lead who rules with an iron fist. Sure, it sucks, but working under such conditions is worse.
[0] https://www.zdnet.com/article/atlassian-estimates-cloud-outa...
I wish the comments were more specific about which features they don’t like. For me a particularly frustrating aspect is the way the UI moves around a lot. I’m quite anxious to click anything until all the loading spinners have stopped in case I click the wrong thing. Then I could be taken to a page or feature I’ve never seen before. Also it’s really annoying when I try to copy something from a ticket description but…
The composer in general. I often have to intersperse log/code lines with prose, and there’s no telling what the Formatting menu will do. Some times selecting a formatting will apply to selected text, sometimes not. Sometimes it will apply when choosing a formatting then pasting text, some times not. Some times it seems to apply to a selection as well as everything after it. It does support Markdown with backticks for…
Earlier quoted context omitted.
Yeah I've been defended Jira here in the past, too. My opinion is that Jira reflects the organisation that manages it. It's basically a whole lot of customizable UI and permissions hanging off a user-defined state machine. You can set it up so that individual teams can fully administer their own projects, or you can go all the way in the other direction and have centralized, locked-down management where you beg some…
Jira doesn't just reflect, it drives convoluted unhelpful bureaucracy. The tool drives the organization to look like the tool wants it to, which is disorganized half broken "organization" with silly overcomplicated rules that give people something to discuss enthusiastically instead of the actual work that needs doing. Jira is organization poison, not just a reflection of what an organization is.
That's the problem with any tool, framework, language, etc where the defenders main argument is, "It's great as long as you don't abuse it." or to put the former bluntly "It's not the tool, it's your organization." Over and over and over again, if an organization is allowed to abuse and misuse something, it eventually will.
Good tooling has opinions and will give you guardrails to not hang yourself.
Earlier quoted context omitted.
> JIRA in its default configuration essentially lets you create anything, anywhere in any state. Anything beyond that is just bad product configuration. That's kind of the point, JIRA has been made into monstrosity at many organizations because the "create anything" mindset.
How does that make it a monstrosity? Unless we're talking about things that are shared across multiple teams, does it really matter how people use it? Nobody is going to care what someone else does in JIRA when they aren't touching that part anyway. Even with 1000 differently configured projects, your 1 or 2 projects you actually work with and configure are the only ones that matter.
Earlier quoted context omitted.
Migration was easy, it was decentralised, had a famous original author & a huge famous project using it and had a lot of "hip" source code platforms such as github, gitorious, bitbucket (pre-atlassian) and gitlab. I'm not surprised it won tbh. Game companies are still using Perforce though.
> Game companies are still using Perforce though. Maybe the ratio of text to non-text assets?