Angular org unit selector always defaults to the consortium with no ancestors or descendants selected

Bug #1908135 reported by Michele Morgan
This bug report is a duplicate of:  Bug #1873322: Angular admin pages "Library" scope. Edit Remove
26
This bug affects 5 people
Affects Status Importance Assigned to Milestone
Evergreen
New
Undecided
Unassigned

Bug Description

The org unit selector common to the Angular admin pages defaults to the top level of the org tree, and neither the +Ancestors nor +Descendants checkboxes are checked. This requires the staff user to set their desired scope each time they visit the page.

The selector should default to the logged in staff user's workstation, and selections for Library, +Ancestors and +Descendants should be sticky.

Revision history for this message
Christine Burns (christine-burns) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.