Swimlanes - Limit number of epics to improve performance
When there are a lot of epics, swimlanes are very slow to load. This board is a good example: https://gitlab.com/groups/gitlab-org/-/boards/1285239?label_name%5B%5D=group%3A%3Aproject%20management&group_by=epic
Here is what's happening: We chain the fetching of ALL epics, 20 by 20 (there are over 3000, and even though only the open ones are being returned here, it's probably still a lot). Then, every time an epic gets loaded, we trigger a separate request to fetch its issues. That is a lot of request and it's obvious the browser is struggling. If we try to scroll it lags and the screen occasionally goes blank for several seconds.
Possible solutions:
- Add
Load more epics
button so the user is the one triggering the fetch of more epics. - Load more epics when clicking
Load more issues
under Unassigned issues lane. Some UX work would be required to make it clear this action fetches epics too. - Guide the user to better scope and filter their boards to avoid too many epics being returned.
cc @uhlexsis
Edited by Florie Guibert