Live data from Hacker News

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

atlassian.com

241–250 of 305 posts

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

#241
post #111

Earlier quoted context omitted.

If you want to make performance a feature, you need to (in order!) * define a metric * measure it automatically with every commit * define a success threshold * make changes to get yourself under the threshold * prohibit further changes which bring you above the threshold Just do it like that for pretty much every view in the system.

As recommended by another poster to take advantage of the technical community here, I have one question and one comment if you can provide more insights: question a) My understanding is that performance numbers fluctuate a LOT, even at sampling in the tens of thousands. Do you have any recommendations of tools or methods to reduce this variance? comment b) we're definitely trying to do this but we're not there yet -…

It’s absolutely baffling for one of the leading tooling providers in the software development cycle they do not have internal competency to...track if their tool actually works or performs, and beyond that they didn’t proactively reach out to customers to at least get verbal direct knowledge while the telemetry was stood up.

Instead they “prioritized” a legal change in the ToS.

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

#242

Earlier quoted context omitted.

who says this is an "issue" its just numbers. If you think its an issue thats your interpretation. For instance I used jira for communicate with my team about 3 projects and it only took me 3 hours. Maybe this person is writing a fiction story where the protagonist is using Jira and they are detailing how they spend their day. Its like a John Steinbeck novel

May I point you to the title of this submission? "Atlassian Cloud ToS section 3.3(I) prohibits discussing performance issues" No sane judge would agree with your interpretation.

No sane judge would accept that that is a valid clause in a ToS.

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

#243

I read HN every day, I never post, I signed up for an account just to post this. I'm a senior PM at a large e-comm company, I was EXTREMELY frustrated with the horrible performance of Jira Cloud, I submitted support tickets to no avail. It's obviously an over-architected broken system. I moved my team to clubhouse, even-though it created an element of fragmentation considering all other teams are using JIRA. I'm so h…

I've tried to convince a particular manager to try GitLab Issues. (We already use GitLab for git/CI anyway).

Seeing that I'm not just the one who thinks it's so ridiculously frustratingly bad-slow [as in, it's impossible to be this slow even after multiple rewrites unless it's some kind of bizarre experiment by Douglas Adams' ghost] will likely lead to us dropping JIRA for good.

Thanks!

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

#244

Earlier quoted context omitted.

See, the irony of this is that you are just publicly sharing performance numbers which undeniably show a pattern of performance issues. It also doesn't seem to be possible without you first accepting ToS. Ooops!

who says this is an "issue" its just numbers. If you think its an issue thats your interpretation. For instance I used jira for communicate with my team about 3 projects and it only took me 3 hours. Maybe this person is writing a fiction story where the protagonist is using Jira and they are detailing how they spend their day. Its like a John Steinbeck novel

> who says this is an "issue" its just numbers. If you think its an issue thats your interpretation.

No, this is a quote from the comment:

"This is what people mean when they say the performance problems are everywhere - viewing issues, viewing boards, viewing comments, opening dropdowns, closing modals? It's all slow."

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

#245
post #142

Earlier quoted context omitted.

It's hard to name a single action I can take in JIRA which does not feel unacceptably slow. However, these are the actions that cause the most issues for me due to being used most often (JIRA datacenter, MBP 2019 with i7 + 32gb ram): 1. Viewing a board. This can take 10+ seconds to load. 2. Dragging an issue from one column to another. This greys out the board, rendering it unreadable and unusable for 5-ish seconds.…

Thank you so much for the details! This is very helpful. I will pass this along to my Jira Perf colleagues (there's multiple of them, since they know Perf is such a big issue). Just to clarify on Search though, which search are you talking about: a) quick search (top bar) b) issue search (the one with the basic/JQL switcher) c) something else Trying to narrow down the latter "even if clicking into any of them is not"…

Do you guys not use the tool? How is this news to you? Couldn’t you self generate this issue list by just sitting in a locked room for 45 minutes and writing down everything you know already doesn’t work?

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

#246

Earlier quoted context omitted.

I did a test for you just now. I have 100Mbps internet, 32GB RAM, 4ghz i7 processor and suchlike. To make it easy for Jira, I'm doing this at a weekend, late at night, during the new years holiday so the servers shouldn't be busy. On a cloud-based classic software project (which has less than 200 issues) opening a link to an issue it takes 4.8 seconds for the page to complete rendering and the progress bar at the top…

Hi michaelt, Thank you for the numbers -> I agree these are slow, and I can guarantee you that the Jira team is working on it (though I can't talk about details). These numbers are definitely outside of the goals. I appreciate the call out of "page to complete rendering and the progress bar at the top of the screen to disappear" and "until the issue, comment and buttons have all loaded". In a dream world of course, e…

> In a dream world of course, everything would load in FWIW our on-prem install uses <1s for opening issues, running a search etc. Too bad that's a dream world you've decided should no longer be...

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

#247

I'm curious, I'm a Cloud customer and I can tell you that the service is incredibly slow even for a small scale setup (2 Jira Projects and 3 Confluence Workspaces). There's an insane amount of network requests seemingly for mouse tracking. By telling everyone here, that Atlassian Cloud products are insufferably slow, am I violating the ToS? I was actually thinking about doing a write up on the issues I've had but thi…

Doesn't Oracle sue if you benchmark them and release the results publicly or is that an old wives tail? On a YouTube lecture at CMU the Materialize guys seemed to try very hard to not even land in the same zip code as that discussion to the point it was awkward, and they seem pretty smart. Are these large organizations really that petty? Ad absurdism, would it be legal if Ford said we couldn’t drag race their car aft…

https://www.oracle.com/downloads/licenses/standard-license.h...

You may not: disclose results of any Program benchmark tests without Oracle’s prior consent

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

#248

Just so everyone is aware, this is Atlassian's stance on that language taken from the internal guidance on the ToS. To be clear I'm not defending this stance as I think it is flawed. But I wanted you guys to know what Atlassians are told about it - ------------------------------------------------------ Section 3.3: Benchmarking Can you explain Atlassian's stance on Benchmarking? Like many other software companies, At…

It's pretty clear in context that they are discouraging detailed performance benchmarks as a proxy for reverse engineering. Not some kind of gag on complaining that "JIRA is too slow".

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

#249

So the language highlighted here is: (i) publicly disseminate information regarding the performance of the Cloud Products; But can we take a minute to talk about the combination of these two : (h) use the Cloud Products for competitive analysis or to build competitive products; (j) encourage or assist any third party to do any of the foregoing. Does this mean as a jira user I can’t help build a jira competitor for a…

Also they changed in MIDFLIGHT. At least only apply it to new customers who have a choice whether to be forced to do this.

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

#250

Earlier quoted context omitted.

I did a test for you just now. I have 100Mbps internet, 32GB RAM, 4ghz i7 processor and suchlike. To make it easy for Jira, I'm doing this at a weekend, late at night, during the new years holiday so the servers shouldn't be busy. On a cloud-based classic software project (which has less than 200 issues) opening a link to an issue it takes 4.8 seconds for the page to complete rendering and the progress bar at the top…

See, the irony of this is that you are just publicly sharing performance numbers which undeniably show a pattern of performance issues. It also doesn't seem to be possible without you first accepting ToS. Ooops!

What are they doing to do? Shut down your instance and force you to switch to a different product....? Hmmmm
Post reply on HN