7 ms·

Yeah I've been defended Jira here in the past, too. My opinion is that Jira reflects the organisation that manages it. It's basically a whole lot of customizab

by vosper 4y ago

Yeah I've been defended Jira here in the past, too. My opinion is that Jira reflects the organisation that manages it. It's basically a whole lot of customizable UI and permissions hanging off a user-defined state machine. You can set it up so that individual teams can fully administer their own projects, or you can go all the way in the other direction and have centralized, locked-down management where you beg some internal specialist Jira admin(s) to make your changes. Also, in the last couple of years it's got a lot better. It's faster, there are options for simpler configuration, and more stuff out-of-the-box (assuming you're on Cloud, but isn't everyone these days?). In detraction: configuring it can be a huge PITA. So many screens, concepts, and so much clicking. But when it's done it works, and I think most of the hassle is just inherent complexity from such a configurable tool (if you haven't Admined Jira: you can change almost anything).

colechristensen 4y ago
Jira doesn't just reflect, it drives convoluted unhelpful bureaucracy. The tool drives the organization to look like the tool wants it to, which is disorganized half broken "organization" with silly overcomplicated rules that give people something to discuss enthusiastically instead of the actual work that needs doing. Jira is organization poison, not just a reflection of what an organization is.
- oneplane 4y ago
  No, it isn't. We have plenty of setups in multiple organisations where even within the org only the administrative settings of the server are locked down and everyone else is free to do whatever they need. Lots of teams just use it as a kanban board, while others setup a state machine-based funnel to process user/business input into usable tickets. JIRA in its default configuration essentially lets you create anything, anywhere in any state. Anything beyond that is just bad product configuration. Now, there are plenty of products out there that suck no matter how you configure it (looking at you, ServiceNow). Especially the comments about "I would rather use trello" seem extremely uninformed as you pretty much *are* trello when you just stick to one kanban board and one project.
  - Ensorceled 4y ago
    > JIRA in its default configuration essentially lets you create anything, anywhere in any state. Anything beyond that is just bad product configuration. That's kind of the point, JIRA has been made into monstrosity at many organizations because the "create anything" mindset.
    - oneplane 4y ago
      How does that make it a monstrosity? Unless we're talking about things that are shared across multiple teams, does it really matter how people use it? Nobody is going to care what someone else does in JIRA when they aren't touching that part anyway. Even with 1000 differently configured projects, your 1 or 2 projects you actually work with and configure are the only ones that matter.
      - colechristensen 4y ago
        Because it attracts somebody 4 layers up to tell somebody 3 layers up to come up with a common Jira platform for everybody and then you don't control how your project is run and then Jira becomes the enemy, a faceless micromanager driving your work life that has strong opinions on how you do everything, a dozen steps that need to be done "right" or you get your half a dozen managers asking if you read the memo about TPS reports, er, Jira tickets.
        oneplane 4y ago
        So that is not a JIRA problem since you can do a > it attracts somebody 4 layers up to tell somebody 3 layers up to come up with a common with pretty much everything, including a spreadsheet or a plain text file. Conflating bad business practises with tool configuration or products in general doesn't help anyone. If a business is very stiff and scared of its employees, they will try out all sorts of useless control methods hoping it will somehow make some metric 'better'. You can do that with Trello too. Doesn't make Trello a bad product, and it doesn't make JIRA a bad product. At the same time, pretending a larger organisation with many teams can function without any form of state tracking is a nice dream but not a reality either, so it's not like you can do without anything at all. But like reposted a bunch of times, how you do it and who is responsible for it is pretty important.
- bragr 4y ago
  Jira is highly flexible and customizable, almost to a fault. One Jira can look and operate almost totally different to another with enough customization. If Jira feels inflexible and bureaucratic to you, I'd argue that's only a reflection of how your Jira admins operate or the rules they are forced to implement.
  - colechristensen 4y ago
    >customizable, almost to a fault Customizable, absolutely to a fault. It is the infinite customizability of a tool targeted towards middle management which is why Jira can go to hell. It is indeed possible to not be in Jira hell, but inflation of complexity is inevitable and almost entirely irreversible. It encourages and accelerates the path towards bureaucratic hell. Any avoidance of this is a temporary aberration.
  - Redsquare 4y ago
    Jira admins....says it all
- snapetom 4y ago
  It seems the pro-Jira comments here are basically, "It's fine if your organization isn't a mess and you don't abuse it." That's the problem with any tool, framework, language, etc where the defenders main argument is, "It's great as long as you don't abuse it." or to put the former bluntly "It's not the tool, it's your organization." Over and over and over again, if an organization is allowed to abuse and misuse something, it eventually will. Good tooling has opinions and will give you guardrails to not hang yourself.
  - carlmr 4y ago
    Exactly, it's the same with C++. You can do great stuff with it as long as every single developer on the project is extremely disciplined and knowledgeable about its pitfalls. As organizations and projects grow you or someone else will at some point hire incompetent people that mess up this delicate balance. Better to have guardrails.
- LaGrange 4y ago
  > Jira doesn't just reflect, it drives convoluted unhelpful bureaucracy. I though so too, but now I no longer believe that's the case. This is because of two reasons: one questions the statement itself - and the other one questions whether the statement correctly identifies the organizational issue. Firstly, almost every tool I ever used for project organization has grown to similar degree of complexity. All _software_ employed was strongly incentivized to implement new mechanisms of automation and regulation - thus right now I would struggle to name a non-defunct and non-single-user tool that doesn't have the issue. And certainly no tool that that I would call "established" - an arbitrary designation, to be sure, but that largely reflects that the complexity almost _defines_ establishment for a project management tool. Secondly, because I think the issue isn't, truly, the _bureaucracy_. Right now I believe it's the _technocracy_. It's the belief that every process has to be codified into software, and enforced in a manner that would make exceptions impossible without a pull request. This leads to - increase in complexity (because corner cases that would be easily solved with a quick email exchange now require weird workarounds - and if they are too common, actual change to the software) - reduction in real organizational flexibility (any special case is now discouraged on a technical level). Worst part is, it's very hard to sell a shift away from this. Technocratic adherence to software-enforced processes became nearly synonymous to "accountability." In itself that's frustrating to me - I believe this serves to paint organizational failures as forces of nature, effectively reducing accountability. But, so far, I have failed to effectively communicate it to most people - with exception of the very few who, themselves, have a considerable interest in social dynamics, one that goes beyond the professional interest expected of a manager. And to those, those are generally truisms - I'm under no impression I'm particularly original here. --- Aaaanyway, I went back to liking Jira - because, under all the cruft, there's still (or at least there still was) the basic bug tracker software that's almost like Bugzilla, but slightly less painful. And I like bug trackers, as long as they're used to track bugs - not manage projects. Projects are managed by people, and these days I believe that the reason all this software, as complex as it is, keeps failing to accurately communicate the project state, is because you would need the software to be a person.
- IOT_Apprentice 4y ago
  Lighten up Francis. Jira is simply a tool. if you care that much, apply to be on the team at your company that defines the workflow rules and strip away what isn't needed.
msbarnett 4y ago
The central problem with JIRA is that, once you've gotten beyond the overly customizable functionality and difficult-to-reason about permissions, and once you've managed to avoid organizations that go too far off of the deep-end and once you've finally found a happy simplicity in a kanban-ish board, once you've done all of that, it is still unbelievably, unjustifiably, just incredibly and amazingly so very very goddamn slow.
- plonk 4y ago
  As someone who uses both, let me recommend to you Microsoft Teams, the only enterprise software that manages to be slower.
- andy_ppp 4y ago
  There’s a screen in jira if you change multiple items with a progress bar. I looked once and the operation seems to happen instantly and the progress bar is just there because of some bad designers ego…
judge2020 4y ago
> It's faster, there are options for simpler configuration, and more stuff out-of-the-box (assuming you're on Cloud, but isn't everyone these days?). My understanding is that the Cloud offering is the slower one, assuming you can dedicate a beefy server (but probably under $200/mo on hetzner or ovh for most businesses) to running your Atlassian stuff.
madmax108 4y ago
"My opinion is that Jira reflects the organisation that manages it." Came here to say EXACTLY this. I've used Jira across 3 companies, and in the first 2, I always felt like folks complaining about Jira were just being picky developers wanting the sun, moon and the stars, because Jira worked perfectly fine for me and my team (in fact, it was the backbone of our process). Then in the third org, I felt like I was hit with a brick wall of every single issue folks complaining about jira point out. Needless workflows, Middle Managers wanting to "control" how stories/epics get closed, multiple levels of convoluted manual configurations, automated processes creating Jiras that for trivial non-issues which clogged notifications and team backlogs and brought jira to a crawl etc. Heck, at one point, the mess got so bad, that the company considered hiring a third party to "fix" our Jira workflows. And note that this was a <100 person startup! On introspecting, I completely felt that in the first 2 companies, the organization was structured around "getting stuff done" and "keeping stuff as simple as possible, but no simpler" and that naturally flowed into how Jira was set up as well, while in the latter, the focus was entirely on top-down "process", and that showed in the Jira setup as well. Honestly, I now think I can say a lot about a company's engineering/product culture just by spending 15 minutes on their Jira ;-)
SamuelAdams 4y ago
This applies to all enterprise software. It’s also called Conway’s Law: Any organization that designs a system (defined broadly) will produce a design whose structure is a copy of the organization's communication structure. https://en.wikipedia.org/wiki/Conway's_law https://en.wikipedia.org/wiki/Conway's_law
lmm 4y ago
It's not a neutral tool. Jira makes micromanagement easy and trusting people hard; you can use it for good, but you're working against the grain of it the whole time. Everything is default deny (issues can only go through approved transitions, by default regular users can't change the available transitions), the default issue forms have way too many mandatory fields, and a bunch of reports that only micromanagers want or need are front and center in the UI.
- pid-1 4y ago
  > the default issue forms have way too many mandatory fields I only fill points and name for my issues. My company never customized anything.
- arcticbull 4y ago
  I find Jira isn't a tracker, it's a tracker construction kit. You can make it be pretty much anything you want - except, you know, fast.
  - Frost1x 4y ago
    I view Jira as the embodiment of the misguided software engineering practice of trying to generalize and abstract too high level of a task of something like "project management" and distill it down into one tool. While the Golden perfect abstraction handed down for the heavens by the gods is what you seek, it ultimately passes down complexity to end users through its generic approach. You need to create opinions within the generic world and then your team needs to understand Jira's abstraction combined with the opinion your company builds around it that's probably not documented. The end result is unless you're running a large project that really requires the functionality possible in Jira where creating the overhead or overloading something simpler isn't practical, then you're probably better off using something simpler and more opinionated--a nice simple solid framework to keep everyone on track.
- xedrac 4y ago
  I realize company-wide planning is extremely hard, especially when there are many inter-dependencies that can block entire departments if a single deadline slips. But in my experience, the only thing that Jira brings to the table is the ability to document, in a centralized place, the pieces of work that need to be done, and what stage they are currently in. In my field, anything software related is really hard to estimate accurately, which makes the whole aggregate estimation in Jira not only worthless, but actively harmful because management will treat it as truth. We could replace Jira with a big whiteboard of TODOs and we'd likely get things done faster, and with higher quality. My favorite excerpt from the site: > Jira is not completely useless: it gives people who usually add negative value to the project a way to appear busy and productive, with associated rewards and promotion opportunities.
throwaway3l2ff 4y ago
Yes, we switched to Jira from a piece of abandonware (simple php based bug tracker) several years ago. Jira is kinda slow sometimes, but not horrible. And yes, like you said, once you get it configured it works great. Overall, we are very happy with Jira and it's worth the cost for the value it brings to the organization (still hurts the wallet, but it's at least justified). ...and then Atlassian comes along and rug-pulls on-prem Jira. We only have ~80 users, so 1000-user-minimum data center isn't going to cut it for us. And there is an on-prem requirement, so no cloud option either (wouldn't want to anyway). And for that, I bitch. Fuck Atlassian and everything they do to appease their shareholders before the customers.
- vosper 4y ago
  Yeah that's a bit rough. Though I think for most people the cloud solution is the way to go, though - even if it's an evil Saas-recurring-revenue play. I was close enough to a previous team that used to admin an on-prem Jira (~7 years ago) to know it wasn't just set-and-forget, and also that almost all the slowness users complained about was due to under-provisioned hardware. Honestly I reckon half of Jira's reputation for slowness could have come from bad on-prem installs. The cloud version is not slow, and Atlassian does do work on performance https://community.atlassian.com/t5/Confluence-articles/Confluence-page-tree-quick-search-inline-comments-and-more-now/ba-p/2038903?utm_source=newsletter-email&utm_medium=email&utm_campaign=confluence-digest-june_EML-12967&jobid=105614824&subid=1682268016 https://community.atlassian.com/t5/Confluence-articles/Confl...
  - capitainenemo 4y ago
    funny you should say that given a bunch of these rants on the article link sound very much like the cloud version in terms of amount of JS loaded and network requests. Also no shortage of folks elsewhere in this discussion talking about cloud slowness. We've had plenty of irritations with our on-prem, but slowness, not so much. And yeah, for us it's mostly about keeping the data internal.
  - cmgbhm 4y ago
    I’m not convinced the cloud version isn’t terribly slow. There’s a ton more indirection for userids. Screens that used to be part of my standard workflow have Ajax handlers. Even name completion is slow. The #1 question answer on the old ui survey workaround asking why are you using the old ui: slowness. Confluence also got clobbered. I can count page load times.

by vosper 4y ago

colechristensen 4y ago

Jira doesn't just reflect, it drives convoluted unhelpful bureaucracy. The tool drives the organization to look like the tool wants it to, which is disorganized half broken "organization" with silly overcomplicated rules that give people something to discuss enthusiastically instead of the actual work that needs doing. Jira is organization poison, not just a reflection of what an organization is.

oneplane 4y ago
No, it isn't. We have plenty of setups in multiple organisations where even within the org only the administrative settings of the server are locked down and everyone else is free to do whatever they need. Lots of teams just use it as a kanban board, while others setup a state machine-based funnel to process user/business input into usable tickets. JIRA in its default configuration essentially lets you create anything, anywhere in any state. Anything beyond that is just bad product configuration. Now, there are plenty of products out there that suck no matter how you configure it (looking at you, ServiceNow). Especially the comments about "I would rather use trello" seem extremely uninformed as you pretty much *are* trello when you just stick to one kanban board and one project.
- Ensorceled 4y ago
  > JIRA in its default configuration essentially lets you create anything, anywhere in any state. Anything beyond that is just bad product configuration. That's kind of the point, JIRA has been made into monstrosity at many organizations because the "create anything" mindset.
  - oneplane 4y ago
    How does that make it a monstrosity? Unless we're talking about things that are shared across multiple teams, does it really matter how people use it? Nobody is going to care what someone else does in JIRA when they aren't touching that part anyway. Even with 1000 differently configured projects, your 1 or 2 projects you actually work with and configure are the only ones that matter.
    - colechristensen 4y ago
      Because it attracts somebody 4 layers up to tell somebody 3 layers up to come up with a common Jira platform for everybody and then you don't control how your project is run and then Jira becomes the enemy, a faceless micromanager driving your work life that has strong opinions on how you do everything, a dozen steps that need to be done "right" or you get your half a dozen managers asking if you read the memo about TPS reports, er, Jira tickets.
      - oneplane 4y ago
        So that is not a JIRA problem since you can do a > it attracts somebody 4 layers up to tell somebody 3 layers up to come up with a common with pretty much everything, including a spreadsheet or a plain text file. Conflating bad business practises with tool configuration or products in general doesn't help anyone. If a business is very stiff and scared of its employees, they will try out all sorts of useless control methods hoping it will somehow make some metric 'better'. You can do that with Trello too. Doesn't make Trello a bad product, and it doesn't make JIRA a bad product. At the same time, pretending a larger organisation with many teams can function without any form of state tracking is a nice dream but not a reality either, so it's not like you can do without anything at all. But like reposted a bunch of times, how you do it and who is responsible for it is pretty important.
bragr 4y ago
Jira is highly flexible and customizable, almost to a fault. One Jira can look and operate almost totally different to another with enough customization. If Jira feels inflexible and bureaucratic to you, I'd argue that's only a reflection of how your Jira admins operate or the rules they are forced to implement.
- colechristensen 4y ago
  >customizable, almost to a fault Customizable, absolutely to a fault. It is the infinite customizability of a tool targeted towards middle management which is why Jira can go to hell. It is indeed possible to not be in Jira hell, but inflation of complexity is inevitable and almost entirely irreversible. It encourages and accelerates the path towards bureaucratic hell. Any avoidance of this is a temporary aberration.
- Redsquare 4y ago
  Jira admins....says it all
snapetom 4y ago
It seems the pro-Jira comments here are basically, "It's fine if your organization isn't a mess and you don't abuse it." That's the problem with any tool, framework, language, etc where the defenders main argument is, "It's great as long as you don't abuse it." or to put the former bluntly "It's not the tool, it's your organization." Over and over and over again, if an organization is allowed to abuse and misuse something, it eventually will. Good tooling has opinions and will give you guardrails to not hang yourself.
- carlmr 4y ago
  Exactly, it's the same with C++. You can do great stuff with it as long as every single developer on the project is extremely disciplined and knowledgeable about its pitfalls. As organizations and projects grow you or someone else will at some point hire incompetent people that mess up this delicate balance. Better to have guardrails.
LaGrange 4y ago
> Jira doesn't just reflect, it drives convoluted unhelpful bureaucracy. I though so too, but now I no longer believe that's the case. This is because of two reasons: one questions the statement itself - and the other one questions whether the statement correctly identifies the organizational issue. Firstly, almost every tool I ever used for project organization has grown to similar degree of complexity. All _software_ employed was strongly incentivized to implement new mechanisms of automation and regulation - thus right now I would struggle to name a non-defunct and non-single-user tool that doesn't have the issue. And certainly no tool that that I would call "established" - an arbitrary designation, to be sure, but that largely reflects that the complexity almost _defines_ establishment for a project management tool. Secondly, because I think the issue isn't, truly, the _bureaucracy_. Right now I believe it's the _technocracy_. It's the belief that every process has to be codified into software, and enforced in a manner that would make exceptions impossible without a pull request. This leads to - increase in complexity (because corner cases that would be easily solved with a quick email exchange now require weird workarounds - and if they are too common, actual change to the software) - reduction in real organizational flexibility (any special case is now discouraged on a technical level). Worst part is, it's very hard to sell a shift away from this. Technocratic adherence to software-enforced processes became nearly synonymous to "accountability." In itself that's frustrating to me - I believe this serves to paint organizational failures as forces of nature, effectively reducing accountability. But, so far, I have failed to effectively communicate it to most people - with exception of the very few who, themselves, have a considerable interest in social dynamics, one that goes beyond the professional interest expected of a manager. And to those, those are generally truisms - I'm under no impression I'm particularly original here. --- Aaaanyway, I went back to liking Jira - because, under all the cruft, there's still (or at least there still was) the basic bug tracker software that's almost like Bugzilla, but slightly less painful. And I like bug trackers, as long as they're used to track bugs - not manage projects. Projects are managed by people, and these days I believe that the reason all this software, as complex as it is, keeps failing to accurately communicate the project state, is because you would need the software to be a person.
IOT_Apprentice 4y ago
Lighten up Francis. Jira is simply a tool. if you care that much, apply to be on the team at your company that defines the workflow rules and strip away what isn't needed.

msbarnett 4y ago

The central problem with JIRA is that, once you've gotten beyond the overly customizable functionality and difficult-to-reason about permissions, and once you've managed to avoid organizations that go too far off of the deep-end and once you've finally found a happy simplicity in a kanban-ish board, once you've done all of that, it is still unbelievably, unjustifiably, just incredibly and amazingly so very very goddamn slow.

plonk 4y ago
As someone who uses both, let me recommend to you Microsoft Teams, the only enterprise software that manages to be slower.
andy_ppp 4y ago
There’s a screen in jira if you change multiple items with a progress bar. I looked once and the operation seems to happen instantly and the progress bar is just there because of some bad designers ego…

judge2020 4y ago

> It's faster, there are options for simpler configuration, and more stuff out-of-the-box (assuming you're on Cloud, but isn't everyone these days?). My understanding is that the Cloud offering is the slower one, assuming you can dedicate a beefy server (but probably under $200/mo on hetzner or ovh for most businesses) to running your Atlassian stuff.

madmax108 4y ago

"My opinion is that Jira reflects the organisation that manages it." Came here to say EXACTLY this. I've used Jira across 3 companies, and in the first 2, I always felt like folks complaining about Jira were just being picky developers wanting the sun, moon and the stars, because Jira worked perfectly fine for me and my team (in fact, it was the backbone of our process). Then in the third org, I felt like I was hit with a brick wall of every single issue folks complaining about jira point out. Needless workflows, Middle Managers wanting to "control" how stories/epics get closed, multiple levels of convoluted manual configurations, automated processes creating Jiras that for trivial non-issues which clogged notifications and team backlogs and brought jira to a crawl etc. Heck, at one point, the mess got so bad, that the company considered hiring a third party to "fix" our Jira workflows. And note that this was a <100 person startup! On introspecting, I completely felt that in the first 2 companies, the organization was structured around "getting stuff done" and "keeping stuff as simple as possible, but no simpler" and that naturally flowed into how Jira was set up as well, while in the latter, the focus was entirely on top-down "process", and that showed in the Jira setup as well. Honestly, I now think I can say a lot about a company's engineering/product culture just by spending 15 minutes on their Jira ;-)

SamuelAdams 4y ago

This applies to all enterprise software. It’s also called Conway’s Law: Any organization that designs a system (defined broadly) will produce a design whose structure is a copy of the organization's communication structure. https://en.wikipedia.org/wiki/Conway's_law https://en.wikipedia.org/wiki/Conway's_law

lmm 4y ago

It's not a neutral tool. Jira makes micromanagement easy and trusting people hard; you can use it for good, but you're working against the grain of it the whole time. Everything is default deny (issues can only go through approved transitions, by default regular users can't change the available transitions), the default issue forms have way too many mandatory fields, and a bunch of reports that only micromanagers want or need are front and center in the UI.

pid-1 4y ago
> the default issue forms have way too many mandatory fields I only fill points and name for my issues. My company never customized anything.
arcticbull 4y ago
I find Jira isn't a tracker, it's a tracker construction kit. You can make it be pretty much anything you want - except, you know, fast.
- Frost1x 4y ago
  I view Jira as the embodiment of the misguided software engineering practice of trying to generalize and abstract too high level of a task of something like "project management" and distill it down into one tool. While the Golden perfect abstraction handed down for the heavens by the gods is what you seek, it ultimately passes down complexity to end users through its generic approach. You need to create opinions within the generic world and then your team needs to understand Jira's abstraction combined with the opinion your company builds around it that's probably not documented. The end result is unless you're running a large project that really requires the functionality possible in Jira where creating the overhead or overloading something simpler isn't practical, then you're probably better off using something simpler and more opinionated--a nice simple solid framework to keep everyone on track.
xedrac 4y ago
I realize company-wide planning is extremely hard, especially when there are many inter-dependencies that can block entire departments if a single deadline slips. But in my experience, the only thing that Jira brings to the table is the ability to document, in a centralized place, the pieces of work that need to be done, and what stage they are currently in. In my field, anything software related is really hard to estimate accurately, which makes the whole aggregate estimation in Jira not only worthless, but actively harmful because management will treat it as truth. We could replace Jira with a big whiteboard of TODOs and we'd likely get things done faster, and with higher quality. My favorite excerpt from the site: > Jira is not completely useless: it gives people who usually add negative value to the project a way to appear busy and productive, with associated rewards and promotion opportunities.

throwaway3l2ff 4y ago

Yes, we switched to Jira from a piece of abandonware (simple php based bug tracker) several years ago. Jira is kinda slow sometimes, but not horrible. And yes, like you said, once you get it configured it works great. Overall, we are very happy with Jira and it's worth the cost for the value it brings to the organization (still hurts the wallet, but it's at least justified). ...and then Atlassian comes along and rug-pulls on-prem Jira. We only have ~80 users, so 1000-user-minimum data center isn't going to cut it for us. And there is an on-prem requirement, so no cloud option either (wouldn't want to anyway). And for that, I bitch. Fuck Atlassian and everything they do to appease their shareholders before the customers.

vosper 4y ago
Yeah that's a bit rough. Though I think for most people the cloud solution is the way to go, though - even if it's an evil Saas-recurring-revenue play. I was close enough to a previous team that used to admin an on-prem Jira (~7 years ago) to know it wasn't just set-and-forget, and also that almost all the slowness users complained about was due to under-provisioned hardware. Honestly I reckon half of Jira's reputation for slowness could have come from bad on-prem installs. The cloud version is not slow, and Atlassian does do work on performance https://community.atlassian.com/t5/Confluence-articles/Confluence-page-tree-quick-search-inline-comments-and-more-now/ba-p/2038903?utm_source=newsletter-email&utm_medium=email&utm_campaign=confluence-digest-june_EML-12967&jobid=105614824&subid=1682268016 https://community.atlassian.com/t5/Confluence-articles/Confl...
- capitainenemo 4y ago
  funny you should say that given a bunch of these rants on the article link sound very much like the cloud version in terms of amount of JS loaded and network requests. Also no shortage of folks elsewhere in this discussion talking about cloud slowness. We've had plenty of irritations with our on-prem, but slowness, not so much. And yeah, for us it's mostly about keeping the data internal.
- cmgbhm 4y ago
  I’m not convinced the cloud version isn’t terribly slow. There’s a ton more indirection for userids. Screens that used to be part of my standard workflow have Ajax handlers. Even name completion is slow. The #1 question answer on the old ui survey workaround asking why are you using the old ui: slowness. Confluence also got clobbered. I can count page load times.