Floating Groups do not scope to specific org units
Bug #1329837 reported by
Erica Rohlfs
This bug affects 4 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Evergreen |
Confirmed
|
Wishlist
|
Unassigned | ||
Bug Description
Evergreen 2.6.1
The ability to configure floating groups should include the ability to specify the context org unit.
For catalogers within a consortium, selecting the applicable Floating Group(s) for their system/branches in the Items Attribute Editor (Floating? Dropdown options) will be more intuitive if the floating groups scope to specific org units. Having the ability to view all of the floating groups within the Floating? dropdown options is not entirely user-friendly.
| Changed in evergreen: | |
| importance: | Undecided → Wishlist |
Revision history for this message
| Josh Stompro (u-launchpad-stompro-org) wrote | #1 |
| Changed in evergreen: | |
| status: | New → Confirmed |
To post a comment you must log in.
Erica, I agree with you on this. It would help remove the possibility of making a mistake when choosing a floating group if you only saw the groups associated with your org units. +1