-
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
[JRACLOUD-85601] Cover Images on TMP boards are not cached and reload when scrolling causing performance hit
| Component/s | Original: Board (Team) - View [ 61966 ] | |
| Component/s | New: Board (Team) - View [ 77899 ] | |
| Key |
Original:
|
New:
|
| Project | Original: Jira Cloud [ 18511 ] | New: Jira Platform Cloud [ 18514 ] |
| Resolution | New: Timed out [ 10 ] | |
| Status | Original: Long Term Backlog [ 12073 ] | New: Closed [ 6 ] |
| Labels | Original: attachements coverimage jsw-s4 performance | New: attachements coverimage jsw-s4 performance timeout-bulk-close202410 |
| Summary | Original: Cover Images on Team managed boards are not cached and reload when scrolling causing performance hit | New: Cover Images on TMP boards are not cached and reload when scrolling causing performance hit |
| Labels | Original: attachements coverimage performance | New: attachements coverimage jsw-s4 performance |
| Assignee | Original: Earl McCutcheon [ emccutcheon ] |
| Assignee | New: Earl McCutcheon [ emccutcheon ] |
| Support reference count | Original: 1 | New: 2 |
| Priority | Original: Low [ 4 ] | New: Medium [ 3 ] |
| Description |
Original:
h3. Issue Summary
[Cover Images|https://community.atlassian.com/t5/Team-managed-projects-articles/You-asked-for-it-so-we-delivered-images-on-issues-have-arrived/ba-p/844691] 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 h3. 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 h3. Expected Results Images that have already been loaded are cached and do not need to be reloaded after initial load h3. 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 h3. Additional note: On a large enough board with many columns and issues with cover images, this could possibly trigger a rate limit h3. 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. !Screenshot 2023-07-24 at 11.20.25 AM.png|thumbnail! |
New:
h3. Issue Summary
[Cover Images|https://community.atlassian.com/t5/Team-managed-projects-articles/You-asked-for-it-so-we-delivered-images-on-issues-have-arrived/ba-p/844691] 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 h3. 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 h3. Expected Results Images that have already been loaded are cached and do not need to be reloaded after initial load h3. 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 h3. 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. !Screenshot 2023-07-24 at 11.20.25 AM.png|thumbnail! |