You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
You can delete datasets from other histories in the Multi-History view, and the dataset will disappear, but the status (active/deleted/hidden count, etc) will not be updated until you set that history as current or reload the page.
Detected during 24.0 release testing
Galaxy Version and/or server at which you observed the bug
Galaxy Version: 23.1
Commit: (run git rev-parse HEAD if you run this Galaxy server)
To Reproduce
Steps to reproduce the behavior:
Open the Multi-history view with some histories
Try to delete some datasets in any of the histories except for the current one
Observe the dataset disappears but the history item counts do not update
Expected behavior
The status of the history should be always in sync with the history.
Screenshots
Additional context
Might be a variant of #17697 that affects 23.1 too
The text was updated successfully, but these errors were encountered:
davelopez
changed the title
Multi-history view: Operating on datasets in other (non-current) histories does not update the status bar
[23.1] Multi-history view: Operating on datasets in other (non-current) histories does not update the status bar
Mar 13, 2024
davelopez
changed the title
[23.1] Multi-history view: Operating on datasets in other (non-current) histories does not update the status bar
[23.1] Multi-history view: Operating on datasets in other (non-current) histories does not update the datasets count status
Mar 13, 2024
Describe the bug
You can delete datasets from other histories in the Multi-History view, and the dataset will disappear, but the status (active/deleted/hidden count, etc) will not be updated until you set that history as current or reload the page.
Detected during 24.0 release testing
Galaxy Version and/or server at which you observed the bug
Galaxy Version: 23.1
Commit: (run
git rev-parse HEAD
if you run this Galaxy server)To Reproduce
Steps to reproduce the behavior:
Expected behavior
The status of the history should be always in sync with the history.
Screenshots

Additional context
Might be a variant of #17697 that affects 23.1 too
The text was updated successfully, but these errors were encountered: