Atlassian Cloud ToS section 3.3(I) prohibits discussing performance issues

What gateways have you been using?! That's a long, long way off on the modern internet. Assuming you mean gateways as in the lines you'd see on a traceroute, more typical might be ~2-5ms on a home router, ~0.5-1.0ms upstream.

> More generally, the issues I see reported only ever seem to be fixed in the Cloud version. I currently have to use the Data Center version.

> Why go through the trouble of reporting an issue I'll never see fixed involving a feature that I loathe using?

I find the same issue with Nessus Professional. They too are trying to funnel everyone into using tenable.io (SaaS nessus scanner). And they also are very resistant in doing much of any changes (other than removing the API) from their onprem solution. But tenable.io keeps getting regular updates.

Worse yet, when you talk to anybody there, the first thing is "Why arent you using tenable.io ?" My response every time is, "Has it been fedramped YET?".. Of course it hasn't. Not entirely sure they even plan on doing that.

For maintaining data integrity and preserving a secure environment, these companies are demanding that we open our networks and store our critical data somewhere we really don't have access to.

I don't want to sound mean, but before discussing performance issues, can we talk about how completely unusable all of Atlassian's products are? I mean this sincerely. I feel bad saying it because I know there are lots of people probably on this site that worked on them. But I literally often have no idea how to proceed when using these products. That's something that hasn't happened to me since before I was a teenager.

As 2 random examples, I've used both Confluence and Crucible in the last month. In Confluence, when I log in I see everything that anyone in my (1,000+ people) organization worked on most recently. People I've never even heard of show up as having edited some random document that doesn't concern me. Meanwhile, I can find no way to list all articles that I created. There's a small list of things I edited or looked at in the last 30 days, but no way to say, "just show me everything I created."

Meanwhile, in Crucible, I literally can't figure out how to do anything. I'm reading through the changes to some source code and adding comments, and after an hour of doing that, it still says I've completed 0% of my review. WTF? And when I start my own code review, every god damned time, it tells me, "You're about to start a review with no reviewers." It then offers me 2 choices: Abandon the review or cancel. I get what "abandon" does. What does cancel do? Cancel the review? Cancel abandoning the review? Why is there no button right there to add reviewers? That's what I most want to do! (And there are no reviewers yet because it literally has not yet given me the option to add them previously in the work flow. WTF?)

You can talk about performance all you want. I won't bother until the products actually perform some useful function. As of now, as far as I can tell, they don't.

I hate to pile on a thread where you're already taking a lot of flack, but this point is really important to the future of Atlassian:

> In a dream world of course, everything would load in As a contractor, I have more or less walked out of or refused interviews on discovering Atlassian toolset was in use. It's not because I hate your tooling (it is visually nice and very featureful), it's because the culture that delivered this software is antithetical to anything I look for in a software project I want to use or contribute to. How can I possibly do my job to any degree of satisfaction when I'm tracking work in a tool that requires 15 seconds between mouse clicks? That is the reality of Jira, and as a result I refuse to use it, or work for people who find that acceptable, because it's a "broken window" that tells me much more about the target environment than merely something about suboptimal bug trackers.

Your page budget should be 100ms max, given all your tools actually do are track a couple of text fields in a pleasing style. Whoever the architecture astronauts are at Atlassian that created the current mess, flush them out, no seat is too senior -- this is an existential issue for your business.

Lol, wasn't expecting that :p

Ocelot would be a better example of an gateway https://github.com/ThreeMammals/Ocelot

Used for scaling up web traffic or creating bff's ( backends for frontends)