Jerome St-Louis opened 9 months ago
|
|||||
Will look into this. |
|||||
OneDev changed state to 'Closed' 9 months ago
|
|||||
State changed as code fixing the issue is committed (a28ba83b) |
|||||
OneDev changed state to 'Released' 9 months ago
|
|||||
State changed as build #3984 is successful |
Type |
Bug
|
Priority |
Normal
|
Assignee | |
Affected Versions |
8.6.2
|
Labels |
No labels
|
Issue Votes (0)
There are at least two parts to this problem:
After making any edit to an issue, for example adding a Child issue to an issue, which is not something that is visible at all in the kanban board, the WebSockets notification seems to initiate a refresh.
Then, if my first column (Backlog) has been scrolled down past the "Load More" state, the five columns of my kanban board refresh not once, but five times (the more load more pages have been scrolled, the more times everything gets refreshed). It seems that scrolling past the Load More on the back log automatically triggers the reloading / refreshing of all other columns of the kanban boards.
Ideally, issues should just be updated and without anything disappearing (no "clear").
This is very distracting as the whole series of refreshes can easily take half a minute.