481–490 of 539 posts
The problems with Jira can be extended to the rest of Atlassian and all of their offerings. Their company culture is very much one of "we're right, no matter how many people bring up the same issues." Things like: - Shoving political messaging into git terminal messages - Renaming "blame" to something else without notifying the userbase ("annotate"? It's been a while) because, despite "blame" being a git term, its us…
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.
That’s insane to me. Atlassian pushes very hard for everyone to use the cloud-hosted version, as the on-prem version is hella expensive. You know, that SaaS app that was recently down for over 2 weeks for some customers.[0] I don’t know many companies that would be OK with having no access to their ticket tracker for an indeterminate length of time. Do you have a customer, or worse, regulatory deadline coming up, and…
Earlier quoted context omitted.
Jira is like democracy, it isn't perfect and is full of flaws, yet it still is better than the alternatives.
> yet it still is better than the alternatives. Not in my experience. I'd much rather use GitHub issues or a range of similar products. Finding and searching works well. Performance is good. Organization is feasible. Labels work fine for customization. > Jira is like democracy, it isn't perfect and is full of flaws, ... Using a pithy cross-disciplinary metaphor to try to bolster support for an argument doesn't do muc…
Developing software for 30+ years.
Before Jira came to be, in-house stuff based in Perl CGIs, Lotus, DOORS. ClearQuest, Bugzilla, among others.
After Jira came to be, Trello, GitHub, Azure DevOps, TFS.
None of them provides the same seamless integration between documentation, code changes, change requests, project management, build pipeline, in-house deployment and quite relevant in enterprise context, customization.
Earlier quoted context omitted.
I think those of us who have had to suffer through ClearQuest, Lotus notes etc have an entirely different scale on how bad things can be compared to those who appear to really really hate Jira today. I'm not a fan of Jira but atleast it loads, eventually.
Those things were like 20 years ago ? JIRA is working years old. We’ve developed better more simple issue trackers since, such as GitHub issues and projects. Much simpler.
Good for casual users, while at the enterprise level everyone wants a different set of 90% Jira features.
It is no accident that Microsoft is turning GitHub into an ecosystem that combines Azure DevOps with GitHub.
Earlier quoted context omitted.
I worked at a company once (not programming, more like an online shop) which did everything via email. And I mean everything . Tickets, issues, orders, repair requsts, refunds, you name it. It worked flawlessly — in fact I haven't been at a place that was as well organized since. And it all came down to one thing: everybody understood that there is only email and that if it isn't an email it will be forgotten and fal…
What was the size of the company? Generally speaking any organisation, given enough time, can establish processes that are better than JIRA with a certain amount of luck. However, that's the best case scenario. It's a standard distribution. Sometimes a 100 person project gets by fine with email. Sometimes it all goes to shit. A tool like JIRA is, on average, a lot better than doing it via email only.
Granted, such a thing would not scale up to infinity, but for that size it was perfect and extremely hackable (just email + SMTP after all).
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…
I claim something more specific. A totally powerless workman who's afraid of his bosses blames his tools.
An individual in the face of indomitable authority blames anything else.
Jira is a wonderful proxy for all the bureaucracy and *managers you hate. So hate Jira, because you're powerless to change anything that matters.
Earlier quoted context omitted.
I agree this is where it goes wrong. Chasing an nice looking burn down chart.
The issue is that software developers (correctly) identify the burndown chart as useless due to estimation in software being a joke. Software developers' mistake is not realizing that "linking the tickets" into Epics that managers can search is hugely important. If the project director has no clue about what tickets people are working on things go south fast . All developers should agree on that.
The only reason stuff gets done as it should it because me and my peers are responsible, and because we have a good understanding of what needs to be done, not because of how things are mapped in JIRA.
Earlier quoted context omitted.
That's interesting. This change certainly came post-SVN. I don't recall that ever being used as an explanation, though. Still, quite a silly thing to do based on the presumption that a benign word hurt a hypothetical person's feelings
Git actually also has annotate : https://git-scm.com/docs/git-annotate
Yes that should be ridiculous.
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…
But yea, I agree, they are trying to solve a huge problem. And good on them for it. I still dislike the results though, and that's ok. We still use it.