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

421–430 of 530 posts

Re: Why Jira Sucks

#421

Post by majewsky »

stefanmichael wrote: post #268
TheFunkyMonk wrote: post #170

Earlier quoted context omitted.

Do you prefer to... not have all the details in front of you for a task you're about to work on?

Generally as a senior dev part of your job description is to figure the details out. Not have them provided for you. As a jr or early mid level you can expect to have the majority of the details ironed out and nicely laid out for you to work on, but someone at some point had to actually figure it out and put it in the ticket. Whether that is you or someone else likely depends on your level, the stage of the company,…

I agree with your assessment, having experienced a gradual shift from junior to senior myself.

As for why the downvotes, hypothesis 1: People might misconstrue your position as "senior ICs are supposed to design the system entirely on their own". I understand you as "management provides the direction and some design constraints, seniors fill in the details, juniors just implement specifications from the seniors", which matches my experience.

Hypothesis 2: Maybe it's a culture thing? I'm guessing from your user name that you're from Europe, and I'm from Germany. Maybe the downvoters are literally coming from a different place? (Don't know how it would be different over there though.)

Re: Why Jira Sucks

#422

Post by Aeolun »

robinjones wrote: post #402
Aeolun wrote: post #142

Earlier quoted context omitted.

It would be nice if any of the alternatives would be in line with Jira cost for a large enterprise. I can’t recommend this to anyone if our cost for issue tracking would quadruple overnight. Not to mention the migration costs...

Jira costs are going to skyrocket soon too since they are sunsetting Jira Server. Opportunity is ripe for competitors.

True, but we’re already on datacenter, so won’t be affected.

Re: Why Jira Sucks

#423

Post by codenesium »

stefanmichael wrote: post #268
TheFunkyMonk wrote: post #170

Earlier quoted context omitted.

Do you prefer to... not have all the details in front of you for a task you're about to work on?

Generally as a senior dev part of your job description is to figure the details out. Not have them provided for you. As a jr or early mid level you can expect to have the majority of the details ironed out and nicely laid out for you to work on, but someone at some point had to actually figure it out and put it in the ticket. Whether that is you or someone else likely depends on your level, the stage of the company,…

Generally the details have been sorted out at some level otherwise how did you estimate it? And the ticket was likely estimated 2 months ago and you may not have been a part of that. I prefer a ticket with as much detail as possible so I'm not making the wrong assumptions.

Re: Why Jira Sucks

#424

Post by [deleted] »

kjd1231 wrote: post #288
joegahona wrote: post #252

Earlier quoted context omitted.

To discuss blockers and what you'll be working on that day. Also many engineers aren't good about updating tickets, ruining it for everyone.

I plan on working on the tickets assigned to me on that day, yesterday, and the next day. If I have blockers I'll type up a slack message. It's not that hard.

[deleted]

Re: Why Jira Sucks

#425

Post by Aeolun »

tootie wrote: post #153
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…

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…

> But it's not for them. It's for managers and stakeholders who have to report progress and who are responsible for budgets.

Yeah. The problem is they now have to report at least 50% less progress because half of s dev’s mental power is dedicated to ignoring or updating Jira.

Re: Why Jira Sucks

#426

Post by jabo »

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…

This is great! Thank you for your work. I'm sure I speak for a lot of other folks in this thread - really looking forward to seeing this in prod!

Re: Why Jira Sucks

#427

Post by Andys »

joegahona wrote: post #252
kjd1231 wrote: post #190

Earlier quoted context omitted.

What bothers me is if I use JIRA, why do I have a meeting every single day telling you what I'm working on. If you care, look at JIRA.

To discuss blockers and what you'll be working on that day. Also many engineers aren't good about updating tickets, ruining it for everyone.

In some cases, maybe they would be better at tickets if not forced to use JIRA.

Re: Why Jira Sucks

#428

Post by robinjones »

denysvitali wrote: post #80
CraigJPerry wrote: post #58

Unpopular opinion: it doesn’t suck. Let me walk that back a bit - I have no experience of the cloudy version which unanimously seems to be derided as slow. Atlassian - you might wanna fix that. Like yesterday. But server (& datacentre) editions - best in class for my money. In terms of features, the Rally / Agile Central (did that just re-brand again?) rollup roadmap view is the only missing feature i crave. Atlassia…

> But server (& datacentre) editions - best in class for my money. Well, performance wise they're as bad as the cloud version. Even when you give the instance a lot of CPU / Memory. The problem is not only the Spring application itself, the DB seems to be missing some indexes or the queries are super badly optimized. God only knows what's really happening under the hood, but my self hosted Jira instance isn't any bet…

No, cloud is slow and has been slow for years. On-premise is quick enough, but only if you ensure you have no slow bottle-necks (DB, spinning disks, heavily shared virtualization).

Jira doesn't use Spring--you may be confusing it with Confluence which does.

Re: Why Jira Sucks

#429

Post by wpietri »

namdnay wrote: post #385
wpietri wrote: post #308

Earlier quoted context omitted.

You express a number of notions here that are part of the fantasy of managerialism [1]. An especially big one is that if we render all important decisions unto a managerial class, they will make optimal choices. If that were true, startups would never succeed, because established companies would use their greater resources and market power to gobble up market niches before startups could get momentum. In practice, ev…

I think it’s important to realise that the vast majority (I’m sure it’s more than 90%) of software development being done is technical people from enterprise A building something to help nontechnical people from enterprise B with process C. That’s not something that startups have ever competed with, for good reason. I love startups and I love working on that space, but you must stay aware that it’s a tiny galaxy with…

Startups compete in the enterprise space all the time, [1], so I don't think your characterization is correct.

I agree that client relations is important, but that's something that happens in many businesses. Like the comment I replied to, you assert that a managerial apparatus is necessary for that. I don't think that's the case. It's true that managerialist-dominated companies often prefer to work with other companies of a similar culture. But that doesn't have anything to do with what makes for efficient software engineering.

[1] e.g.: https://www.computerworld.com/article/3412380/the-hottest-en...

Re: Why Jira Sucks

#430

Post by joegahona »

Andys wrote: post #427
joegahona wrote: post #252

Earlier quoted context omitted.

To discuss blockers and what you'll be working on that day. Also many engineers aren't good about updating tickets, ruining it for everyone.

In some cases, maybe they would be better at tickets if not forced to use JIRA.

Yeah, no arguments from me. I'd rather watch someone read a book than use Jira.
Post reply on HN