Re:Atlassian Cloud ToS section 3.3(I) prohibits discussing p...
by confluence_perf on Saturday January 02, 2021 @04:01PM
(#25616486)
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" part to understand which view that is
Re:Atlassian Cloud ToS section 3.3(I) prohibits discussing p...
by texasbigdata on Saturday January 02, 2021 @08:22PM
(#25618447)
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?
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.
3. Editing a field. I get a little spinner before it applies for 2-3s for even the simplest edits like adding a label.
4. Interacting with any board that crosses multiple projects. A single project board is bad enough, as in point 1, but we have a 5 project board that takes 20+ seconds.
Actually, I found an action that's pretty ok: Search results are fast, even if clicking into any of them is not. I'm not sure why rendering a board is so different performance wise.