-
Suggestion
-
Resolution: Unresolved
-
None
-
4
-
8
-
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
The system should be designed with much heavier use of cache on all levels.
Some examples of poor design in Jira that your dev team should attend to:
- Trying to edit a comment, there's no reason for an Ajax request to load the dialog. The text is in the page and so are the edit tools. Only ajax request should be on updating it.
- Trying to change assignee on an issue would load the users list via Ajax request. Why not cache this in localstorage?
There are many more occasions where needless requests are made and the system thus responds much slower than needed. Perhaps it becomes more evident on the cloud service which is obviously overloaded. I could now see that refresh a simple issue page would take 1.1-2.5 seconds to fetch the HTML part of the page (without resources). This should have constantly been under 1sec and the changes clarify the server is overloaded.
- is related to
-
- Gathering Interest
[JRACLOUD-64097] Improve Cloud platform performance
We're experiencing this too. Pages are sluggish, loading an issue is sluggish, entering into edit mode into anything is sluggish, searching is sluggish, dropdowns, etc.
Jira used to feel really good to work in, but it's really starting to feel bad.
It's extremely frustrating that I can type faster than Jira can load. I always have to go back and fix the :check_mark: emoji or re-enter information because of the lag. It's disrupting my work flow pretty bad and as the only QA on my team, I need to be able to work quickly as I have 3 devs pushing work usually at the same time.
Additionally, with the performance improvements, you guys should fix the pasted image issue. When forming an issue and pasting a picture (i take 1000's of screen shots, i'm not saving every screen shot to my computer, which was suggested on another form) and create the issue, the pasted image is not retained and displays as "Preview Unavailable". I always have to create the issue and then go add the image again, leave the issue and then check AGAIN if the image displays correctly because sometimes it doesn't even when editing the description and not initially creating the issue.
Feeling the same problem here. I think that Service Management Projects are way much slower then Software Projects. It's really becoming a pain to work with.