4 ms·

I'm genuinely interested: is this really true? Is Jira necessarily slow when there's a lot of stuff in it? I'm not sure I believe it. There are graph-of-object

I'm genuinely interested: is this really true? Is Jira necessarily slow when there's a lot of stuff in it? I'm not sure I believe it. There are graph-of-objects-plus-metadata applications out there that are pretty fast. I'm not an expert in this domain, but I bet an issue tracker can be made that doesn't feel painful at real scales.

elithrar 6y ago
I didn't interpret the OP to mean slow from an "application performance" perspective - instead, as slow from a "process" perspective. The ticket needs to be filed in the right queue. It needs the "right" tags. It needs to traverse the "approved" workflow correctly. It didn't get assigned to the right epic. etc, etc, etc. It's all of that - the process built up over time, in response to organic needs - that makes things "slow" and drives such a rejection of these tools by developers and their teams. We (collectively) rarely step back and say "what process can we cut?" - only when we use a new tool do we have the chance to address that.
- dpc_pw 6y ago
  It's both. JIRA can often be terribly slow. Each page loads about 10 seconds for me, and I don't know why. Other people say it is ~2s for them. I suspect it has something to do with networking and amount of requests being made, etc. Then, on top of it the flows in Jira can be super slow, which is another story.
fredfjohnsen 6y ago
No, it is not really true. It is completely false & you are correct to question it.
jayparth 6y ago
What's your question here? The premise of the OP is that they created a fast issue tracker. People complain about Jira being slow (me being one of them.) No one has claimed that all issue trackers are slow. ClickUp, Hive, Linear, are all snappy.
- robotresearcher 6y ago
  The comment I replied to said that trackers are slow because they are full of stuff, and when you try a new tracker it feels fast because of lack of stuff.
  - jayparth 6y ago
    I think you might be misinterpreting him. When I read that, "full of stuff" meant old tickets, process that you had to go to, etc. Slow =/= app performance but general cruft. I don't think he literally meant that the app's performance was slowed down by the volume of tickets. I don't think Jira's performance gets much worse even with 10,000s of tickets in it. The baseline performance of the web app is just baseline bad though.
    - robotresearcher 6y ago
      Here's the quote: "New issue trackers feel faster for the same reason switching browsers tends to feel faster—you're getting rid of all of the crap you piled up in the old one. Don't migrate your backlog, start with only a couple engineers in a new issue tracker, and suddenly, wow!, this new tool is so much better!" I guess it can be read either way.

elithrar 6y ago

I didn't interpret the OP to mean slow from an "application performance" perspective - instead, as slow from a "process" perspective. The ticket needs to be filed in the right queue. It needs the "right" tags. It needs to traverse the "approved" workflow correctly. It didn't get assigned to the right epic. etc, etc, etc. It's all of that - the process built up over time, in response to organic needs - that makes things "slow" and drives such a rejection of these tools by developers and their teams. We (collectively) rarely step back and say "what process can we cut?" - only when we use a new tool do we have the chance to address that.

dpc_pw 6y ago
It's both. JIRA can often be terribly slow. Each page loads about 10 seconds for me, and I don't know why. Other people say it is ~2s for them. I suspect it has something to do with networking and amount of requests being made, etc. Then, on top of it the flows in Jira can be super slow, which is another story.

fredfjohnsen 6y ago

No, it is not really true. It is completely false & you are correct to question it.

jayparth 6y ago

What's your question here? The premise of the OP is that they created a fast issue tracker. People complain about Jira being slow (me being one of them.) No one has claimed that all issue trackers are slow. ClickUp, Hive, Linear, are all snappy.

robotresearcher 6y ago
The comment I replied to said that trackers are slow because they are full of stuff, and when you try a new tracker it feels fast because of lack of stuff.
- jayparth 6y ago
  I think you might be misinterpreting him. When I read that, "full of stuff" meant old tickets, process that you had to go to, etc. Slow =/= app performance but general cruft. I don't think he literally meant that the app's performance was slowed down by the volume of tickets. I don't think Jira's performance gets much worse even with 10,000s of tickets in it. The baseline performance of the web app is just baseline bad though.
  - robotresearcher 6y ago
    Here's the quote: "New issue trackers feel faster for the same reason switching browsers tends to feel faster—you're getting rid of all of the crap you piled up in the old one. Don't migrate your backlog, start with only a couple engineers in a new issue tracker, and suddenly, wow!, this new tool is so much better!" I guess it can be read either way.