6 ms·

Here's a benchmark for you, Atlassian: your software is slow as molasses and getting worse with each redesign.

imglorp 8y ago
It seems like they're balancing features with speed. In order to get a bunch of extra features, every page load needs to be 200mb of extra crap that 99% of users won't use 99% of their page views. Oh and hamburger menus are hiding the key features you DO use every page view.
- ethbro 8y ago
  I always thought of Atlassian projects as inheriting all the problems of Java, exposed in UX form.
  - ex_atlassian 8y ago
    Its always the people/expertise, rarely the tool or language.
    - ethbro 8y ago
      Fair. But for purposes of language = ecosystem, I'd definitely say organizations trend to mimic language structure, and vice versa. At least to a first order, palm-reading, internet comment approximation. ;) Modern Java, IBM C# .NET, Microsoft React, Facebook Rust, Mozilla
      - anothergoogler 8y ago
        I'm not sure what's more concerning, that you're calling React a programming language or that you're unaware that Facebook is written in PHP.
        ethbro 8y ago
        I believe you missed the point for the trees. And for the record, I'm under no illusion that Firefox is fully written in Rust either. :p https://4e6.github.io/firefox-lang-stats/ https://4e6.github.io/firefox-lang-stats/
- beerlord 8y ago
  Why doesn't JIRA offer a native desktop app? Everyone using it is on PC, Mac or Linux right? And then a cut-down iOS (iPhone and iPad) app covers the rest?
  - ygra 8y ago
    A few colleagues use a Visual Studio extension, although that seems to be mostly handy for time-tracking and limited interaction with issues. It's also stuck in a UI that goes back to 2008, so perhaps rather fitting ;)
  - arbie 8y ago
    An Electron wrapper around the web app will do wonders for productivity and RAM utilization.
nixpulvis 8y ago
Yea, they didn't say anything about UX complaints, for which there are MANY.
- ygra 8y ago
  You don't like up to seven toolbars on a single page?
dbg31415 8y ago
The new design for Jira really sucks, has made everything slower, and crappier to use. Page load times of 10+ seconds are common. And no clear usability gains. I was a huge fan, but any more I just want to use GitHub.
- Karunamon 8y ago
  Please talk to your admins! In my experience, Most Jira slowdown issues can be traced back to permission checks. (And you can enable tracing in the system settings to verify this) If only your team needs to access it, set the instance to open permissions (I.e. most rights are set to “Everyone”) and then control access using the network or with a proxy in front. This took the instance I run at $dayjob from infuriatingly slow to no slower than any other web application. —Source: 5 years and counting Jira admin
  - dasmoth 8y ago
    This is knowledge that could come in handy one day, so thanks. But fine-grained permissions are a fairly regularly cited reason for using Atlassian’s stuff over other (simpler...) offerings. This sounds a lot like “don’t try the fancy stuff because it’s unusably slow”.
    - Karunamon 8y ago
      I'd be willing to bet part of that is too many fine-grained permissions. It's a bit of a footgun. Basically, anytime you hit a ticket's page, Jira has to scan your account's group memberships and compare that against a litany of permissions to determine whether you can even see the ticket and what actions you can take with each of its fields. This is done to avoid showing you UI elements for things you can't do. If a given permission is set to "everyone", the check simply isn't done (kinda the equivalent of replacing a call to the user directory with a "return true;") I'm not talking entirely about reducing security here. I mean that if everyone in your team is a member of a certain security group, and only your team touches your Jira, set that permission to "everyone" rather than using that security group - the lookup is completely unnecessary in this case. Basically, you want as few permissions as possible to ensure the level of security you actually need. Often this isn't done, people go a bit crazy with permissions schemes trying to segregate this and that.

It seems like they're balancing features with speed. In order to get a bunch of extra features, every page load needs to be 200mb of extra crap that 99% of users won't use 99% of their page views. Oh and hamburger menus are hiding the key features you DO use every page view.

ethbro 8y ago
I always thought of Atlassian projects as inheriting all the problems of Java, exposed in UX form.
- ex_atlassian 8y ago
  Its always the people/expertise, rarely the tool or language.
  - ethbro 8y ago
    Fair. But for purposes of language = ecosystem, I'd definitely say organizations trend to mimic language structure, and vice versa. At least to a first order, palm-reading, internet comment approximation. ;) Modern Java, IBM C# .NET, Microsoft React, Facebook Rust, Mozilla
    - anothergoogler 8y ago
      I'm not sure what's more concerning, that you're calling React a programming language or that you're unaware that Facebook is written in PHP.
      - ethbro 8y ago
        I believe you missed the point for the trees. And for the record, I'm under no illusion that Firefox is fully written in Rust either. :p https://4e6.github.io/firefox-lang-stats/ https://4e6.github.io/firefox-lang-stats/
beerlord 8y ago
Why doesn't JIRA offer a native desktop app? Everyone using it is on PC, Mac or Linux right? And then a cut-down iOS (iPhone and iPad) app covers the rest?
- ygra 8y ago
  A few colleagues use a Visual Studio extension, although that seems to be mostly handy for time-tracking and limited interaction with issues. It's also stuck in a UI that goes back to 2008, so perhaps rather fitting ;)
- arbie 8y ago
  An Electron wrapper around the web app will do wonders for productivity and RAM utilization.

nixpulvis 8y ago

Yea, they didn't say anything about UX complaints, for which there are MANY.

ygra 8y ago
You don't like up to seven toolbars on a single page?

dbg31415 8y ago

The new design for Jira really sucks, has made everything slower, and crappier to use. Page load times of 10+ seconds are common. And no clear usability gains. I was a huge fan, but any more I just want to use GitHub.

Karunamon 8y ago
Please talk to your admins! In my experience, Most Jira slowdown issues can be traced back to permission checks. (And you can enable tracing in the system settings to verify this) If only your team needs to access it, set the instance to open permissions (I.e. most rights are set to “Everyone”) and then control access using the network or with a proxy in front. This took the instance I run at $dayjob from infuriatingly slow to no slower than any other web application. —Source: 5 years and counting Jira admin
- dasmoth 8y ago
  This is knowledge that could come in handy one day, so thanks. But fine-grained permissions are a fairly regularly cited reason for using Atlassian’s stuff over other (simpler...) offerings. This sounds a lot like “don’t try the fancy stuff because it’s unusably slow”.
  - Karunamon 8y ago
    I'd be willing to bet part of that is too many fine-grained permissions. It's a bit of a footgun. Basically, anytime you hit a ticket's page, Jira has to scan your account's group memberships and compare that against a litany of permissions to determine whether you can even see the ticket and what actions you can take with each of its fields. This is done to avoid showing you UI elements for things you can't do. If a given permission is set to "everyone", the check simply isn't done (kinda the equivalent of replacing a call to the user directory with a "return true;") I'm not talking entirely about reducing security here. I mean that if everyone in your team is a member of a certain security group, and only your team touches your Jira, set that permission to "everyone" rather than using that security group - the lookup is completely unnecessary in this case. Basically, you want as few permissions as possible to ensure the level of security you actually need. Often this isn't done, people go a bit crazy with permissions schemes trying to segregate this and that.