Bug #22115
closed
Collection's versions browser at the right-side bar is not accesible on the collection viewer
Description
Steps to reproduce:
- Log into workbench and click on a collection
- In the details panel click on the version number link
- The right-side bar will appear showing the details of the parent project
Workaround:
- Log into workbench and click on a collection
- Navigate to the desired collection's parent project
- Click on the data explorer row belonging to the desired collection
- Click on the "View details" action bar if the right-side bar isn't already visible
- The collection details and versions tabs should be visible (and also will continue to be visible if loading the collection page)
Updated by Peter Amstutz 3 months ago
- Target version changed from Development 2024-09-25 sprint to Development 2024-10-09 sprint
Updated by Lisa Knox 3 months ago
22115-collection-version-browser @ 44c6b224ded19cd6e5297dbf7311f7bb34ee31bf
developer-run-tests-services-workbench2: #1201
- ✅ All agreed upon points are implemented / addressed.
- - Anything not implemented (discovered or discussed during work) has a follow-up story.
- ✅ Code is tested and passing, both automated and manual, what manual testing was done is described
Tried to reproduce bug manually - - Documentation has been updated.
- ✅ Behaves appropriately at the intended scale (describe intended scale).
Intended scale is a single user viewing a single collection. - ✅ Considered backwards and forwards compatibility issues between client and server.
No changes - ✅ Follows our coding standards and GUI style guidelines.
Updated by Stephen Smith 3 months ago
This seems to still have a bug - when I navigate to a collection and click the version number it opens the details panel for the parent project. Only selecting the checkbox for the collection while viewing the parent project before navigating to the collection and clicking on the version number gets the version history to show up.
Updated by Lisa Knox 3 months ago
22115-collection-version-browser @ 7ab9a62c849d21198ac05854d1d30c7347625eb
developer-run-tests-services-workbench2: #1206
I fixed the bug, then adjusted my fix to get the tests to pass, and didn't notice that in doing so I re-introduced the original bug. Should be good now.
Updated by Lisa Knox 3 months ago
- Status changed from In Progress to Resolved
Applied in changeset arvados|e9e4383ec7f60a22cb3b8e0afc4ffa412e965e91.