-
Bug
-
Resolution: Timed out
-
Medium
-
2
-
Minor
-
Issue Summary
Cover Images will only load visible images for the current position on a team-managed board, when scrolling down the images are no longer in view they are not cached, and scrolling the issue back into view will trigger a new fetch to re-load the images, on boards with a lot of columns and many issues this causes a lot of performance overhead taking multiple seconds to reload images when scrolling up and down
Steps to Reproduce
- Create a team-managed project
- create enough issues to be able to scroll through the issues on the sprint view
- add issues to a sprint and start the sprint
- Navigate to active sprint
- Add an attachment to all the issues
- Load the network tab of the browser console to observe the fetch calls
- Scroll down and then back up a few times
Expected Results
Images that have already been loaded are cached and do not need to be reloaded after initial load
Actual Results
Jira relaunches the fetch calls repeatedly to the blob store to load the image again with each time you scroll up or down, an example can be seen in the video here:
- https://www.loom.com/share/efa0101387f94ee18b988265b7b000d5?sid=d8621b05-9a7c-4753-affc-9451f915b6d4
Workaround
This can be done by navigating to the Configure board >> Cards cover images and selecting the slider to disable cover images for the larger board.
- is related to
-
JRACLOUD-85663 Make Next-gen boards with hundreds of cards snappier
- Closed
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JRACLOUD-85601] Cover Images on TMP boards are not cached and reload when scrolling causing performance hit
Hi everyone,
Thank you for previously raising this bug and bringing it to our attention.
Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira users.
As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know.
Thank you again for providing valuable feedback to our team!
Jira Cloud team
Hi Dirk,
If it isn't too much trouble do you mind doing the following so we can retrieve a bit more context around the problem?
1. Open your board (preferably one with lots of cover images)
2. Open the chrome developer tools
3. Navigate to the network tab (within the developer tools) and ensure the `disable cache` checkbox is not selected
4. Scroll until some of the cards with cover images are not visible
5. Scroll back up such that the cards with cover images are visible again
6. Take a screenshot of the last 10 network requests for those card covers and post back here (it shouldn't contain any sensitive data but if it does please be sure to crop it out or blur it out)
I want to see if your chrome is caching any part of the network requests to disk at all or if something else is happening so we can devise a fix for the problem.
Thanks,
Will
Long Term backlog? Shouldn't this be higher priority, it'a a pretty big bug.
Not only causes a performance hit, but it also causes you to mis click on the wrong issues as they're moving around while you try to click. This leads to a lot of anger...
That's annoying, I would still keep the bug open and in the backlog as it's still a major issue for many users.