Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Why Jira Sucks

whyjirasucks.com

Post reply on HN
Print view View original

521–530 of 530 posts

Re: Why Jira Sucks

#521

Post by stephen_g »

Aeolun wrote: post #134
stephen_g wrote: post #56

What’s killing Jira and the other tools in Atlassian’s suite for us is them killing off the on-premises server products. Some of the companies I work with have defense security requirements and just can’t use it in the cloud (unless they followed a lot of stringent requirements that are not on their roadmap, and I assume they would charge a lot more for that). The cloud versions are also far more expensive and while…

Jira datacenter is too expensive too?

Yeah, we’re on 25 and 50 user licenses for the various products (~$3000-$5000 p/a). Datacenter’s lowest tier is 500 users for $40,000 p/a.

Re: Why Jira Sucks

#522

Post by dbbk »

devdas wrote: post #514
dbbk wrote: post #439

Earlier quoted context omitted.

Developers absolutely should not be deciding what is 'priority'. It's very unlikely they have access to the metrics, wider business strategy, internal and external stakeholders, necessary to determine this. That is the job of the Product Manager.

Developers should then be given access to those details so they can make better decisions.

You want essentially a hybrid product manager and developer role? That would be way too much for one person. There wouldn't be enough time.

Re: Why Jira Sucks

#523

Post by nlh »

ccwilson10 wrote: post #383
jabo wrote: post #368

Earlier quoted context omitted.

I appreciate you jumping into a thread like this and it's great to hear that effort is being invested to speed up Jira Cloud. However: > we've been able to load about 100 issues in ~1-2 seconds. I'm sure there are a ton of things that go into speeding things up and I don't mean to diminish the amount of work involved, but might I suggest raising the performance bar even higher? Is there a world where loading 100 issu…

Haha fair enough. The issue will be, and currently mostly is, the effect you see on performance at scale. Small instances don't have instantaneous interactions but they're still much faster. Here's a quick video ( https://imgur.com/a/8ZJrhMZ ) of a dev instance (slower than prod) with the new feature. Loading of this view feels way faster than the board does. The work I'm doing is separate from the performance improv…

I'll chime in and say thank you as well! (Both for your work on this and for addressing it in this thread). Looking forward to seeing the improvements too.

Re: Why Jira Sucks

#524

Post by IshKebab »

epriest wrote: post #517
IshKebab wrote: post #508

Earlier quoted context omitted.

Err, I think you misunderstood. You have to pay to comment on issues about Phabricator . On their official bug tracker. Like, if you find a bug, or a solution for a known bug, you can't tell them without paying. Doesn't have anything to do with cloud hosting our self-hosting.

This is not accurate. You can report bugs, etc., on the community forum here, which has open registration: https://discourse.phabricator-community.org/

That's not a bug tracker.

Re: Why Jira Sucks

#526

Post by yakubin »

IshKebab wrote: post #508
yakubin wrote: post #115

Earlier quoted context omitted.

> You also have to pay to even comment on issues. OP mentioned "non-cloud", so I assumed they wanted it self-hosted. You don't have to pay anyone for commenting in Phabricator when you're self-hosting it.

Err, I think you misunderstood. You have to pay to comment on issues about Phabricator . On their official bug tracker. Like, if you find a bug, or a solution for a known bug, you can't tell them without paying. Doesn't have anything to do with cloud hosting our self-hosting.

Oh. I think that's a fair thing to do. Jira support isn't free either.

Re: Why Jira Sucks

#527

Post by leokennis »

Lazare wrote: post #119

There's a hundred small issues with Jira, but there's one huge one: It's slow. Really, really slow. Atlassian seems to make a lot of money, so I guess they're optimising for something that matters to someone , but from my point of view I have a simple process for evaluating tools: 1) Can I use it at all ? 2) How many of the features I want does it have? I'm pretty sure Jira would score great on the second question, b…

A year ago, for backlog management we migrated from JIRA to ServiceNow.

You don’t know how good you have it with JIRA.

Re: Why Jira Sucks

#528

Post by Viliam1234 »

dblohm7 wrote: post #304
tootie wrote: post #153

Earlier quoted context omitted.

I 100% disagree. Fixing a bug or delivering a feature where you haven't documented the process, (how the criteria were decided, when it was tested and deployed) is as good a running a web site nobody visits. JIRA hate comes from the bottom up. Developers don't like having to have their work parceled out so specifically. But it's not for them. It's for managers and stakeholders who have to report progress and who are…

> Developers don't like having to have their work parceled out so specifically. But it's not for them. It's for managers and stakeholders who have to report progress and who are responsible for budgets. So much for Agile!

Seems like the only refactoring supported by Agile is managers refactoring Agile itself.

Re: Why Jira Sucks

#529

Post by devdas »

dbbk wrote: post #522
devdas wrote: post #514

Earlier quoted context omitted.

Developers should then be given access to those details so they can make better decisions.

You want essentially a hybrid product manager and developer role? That would be way too much for one person. There wouldn't be enough time.

Developers and operations should absolutely have input. They might not make the final decision, but they should have an informed say in the topic.

Re: Why Jira Sucks

#530

Post by troyintokyo »

polote wrote: post #133
SideburnsOfDoom wrote: post #84

To me, what sucks about JIRA (and would suck about any well-designed tool that replaces it) is not "feature x" but the entire JIRA mentality. All of it. It encourages micro-management. It encourages more and more process. It is the enemy of getting better at the DORA metrics, which requires streamlining process. tickets in JIRA are not the work itself, never was and never will be, it is a LARP of the work, but it get…

Any better software to replace it ?

Maybe try with zentao.pm for a scrum tool, self-hosted, open source version available.
Post reply on HN