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

Happy 20th birthday Jira You suck so bad

rida.dev

Post reply on HN
Print view View original

71–80 of 86 posts

Re: Happy 20th birthday Jira You suck so bad

#71

Post by manholio »

lbriner wrote: post #17

What I find shocking about this, as with many other examples from Meta, Alphabet, Amazon etc. is that many of the complaints are things that small companies justify as "yes, but small team". In other words, our 3 developers don't have the time to refactor this API heavy interface because we are struggling with company growth. When you have the size and money of Atlassian, that excuse is pathetic. Yeah we have 3000 De…

> I always thought that these companies were the ones who invented "how to do good web apps"

No. These companies were the first to get a critical mass in their respective markets or product categories. then they used that position to smother or buy out competitors and ensure their survival.

There is nothing mythical or extraordinary about what those companies did, just some mediocre people who were in the right place at the right time.

Re: Happy 20th birthday Jira You suck so bad

#72

Post by prng2021 »

iso1631 wrote: post #62
polotics wrote: post #40

JIRA sucks indeed, but I have seen worse. My pet peeve with Atlassian is that they purchased Trello, and I was really rooting for Trello to refresh the landscape....

Trello was a danger to Atlassian, thus it was bought. Basic capitalism, don't allow a competitor

Capitalist countries allow competitors. Companies allow competitors. Yahoo did not buy Google.

Re: Happy 20th birthday Jira You suck so bad

#73

Post by turtleyacht »

Automation in Jira has improved:

  - You can now trigger Status to Done 
    after merging Github pull request.
  - If someone assigns you a story as 
    reviewer, you can trigger the Status to 
    In Progress (if not already).
  - You can have a story automatically 
    reassign to the reporter once it's 
    marked Done.
These scenarios reduce the need to switch tabs or click, click dropdowns, which is nice.

It would be nice if we could do requirements tracing from business all the way to ITSM change request, track associated defects--some combination of semantic analysis and code grepping--and ultimately dashboard all this.

It seems like it would approach the model of a thinking organism.

Re: Happy 20th birthday Jira You suck so bad

#74

Post by fancy_pantser »

manuel_w wrote: post #41

I have been promoted to Team Lead recently and while I saw Jira as a burden while being a dev, I now totally rely on it to keep on overview. We're currently looking into outphasing Jira and going to GitLab, but as I see, you can't nest tickets there. Can you? This is absolutely crucial to me. I'm happy for recommendations that allow ticket nesting (Epic, Issue, Subissue) and interface nicely with GitLab. Thanks!

Linear

Re: Happy 20th birthday Jira You suck so bad

#75

Post by eurasiantiger »

haswell wrote: post #60
eurasiantiger wrote: post #58

Earlier quoted context omitted.

- Literally never been a problem for me, but maybe not everyone is always connected to gigabit ethernet - Just go to the issues browser where you can see and search for literally all the issues?

1. Jira speed is rarely limited by internet bandwidth. It’s a very slow product in many implementations. Your gigabit internet likely has nothing to do with the performance you experienced, but also correct: not everyone is on a gigabit connection. But if you need a gigabit connection to experience Jira properly, that’s unacceptable. 2. Is your experience with a vanilla instance and/or a small ticket volume?

Some enterprise offering, project scale in thousands of tickets before go-live.

Now that I think about it, perhaps money buys performance here.

Re: Happy 20th birthday Jira You suck so bad

#76

Post by haswell »

eurasiantiger wrote: post #75
haswell wrote: post #60

Earlier quoted context omitted.

1. Jira speed is rarely limited by internet bandwidth. It’s a very slow product in many implementations. Your gigabit internet likely has nothing to do with the performance you experienced, but also correct: not everyone is on a gigabit connection. But if you need a gigabit connection to experience Jira properly, that’s unacceptable. 2. Is your experience with a vanilla instance and/or a small ticket volume?

Some enterprise offering, project scale in thousands of tickets before go-live. Now that I think about it, perhaps money buys performance here.

Especially if it is self hosted.

The other thing that seems to commonly happen is the customize-ability of these systems leads to major per-transaction overhead/bloat as custom business logic on its 400th revision is executing with ever more db-impacting logic.

Re: Happy 20th birthday Jira You suck so bad

#77

Post by LilBytes »

9wzYQbTYsAIc wrote: post #70
LilBytes wrote: post #53

Earlier quoted context omitted.

I can only infer that you've never used SharePoint. As both a user and both as a Product or Project manager, it's worse in almost every metric. Atlassians products sick but they're strides better than their competitors which says more about the industry than anything else.

I can infer that you may not have used SharePoint recently or any of the Azure project management suite. That ecosystem has gotten drastically better in the past half decade.

I'm using Sharepoint and Azure DevOps boards now, Atlassian was last used 3+ years ago.

Re: Happy 20th birthday Jira You suck so bad

#79

Post by ridafkih »

gw99 wrote: post #3

JIRA does not suck as bad as that thing following my cursor on that site and believe me I dislike JIRA a lot.

Was trying to figure out why my website randomly got way above its normal daily usage, looks like I found it.

FWIW, I went ahead and removed it on the blog post pages.

Re: Happy 20th birthday Jira You suck so bad

#80

Post by ridafkih »

fortnum wrote: post #24

Isn't it ironic that this complaint is posted on a site which hijacks your mouse cursor? Speaking of usability ;)

It shouldn't hijack it, but you're the second to complain on this specific topic, so I went ahead and removed it on the blog post screens.

I was initially trying to figure out if someone was DDoS'ing my website, but it seems as though the post just made it to HN. :P

Post reply on HN