Wish List - Show all values for a setting on Angular Library Settings Editor

Bug #1965542 reported by Terran McCanna
24
This bug affects 5 people
Affects Status Importance Assigned to Milestone
Evergreen
Confirmed
Wishlist
Unassigned

Bug Description

This is a wish list for the Angular version of the Library Settings Editor work at https://bugs.launchpad.net/evergreen/+bug/1839341

It would be useful to have the option to select a particular setting and be able to see all the org units that have values set for it.

As an example, I'd like to be able to click on the setting for "Enable Stripe payments" to see which branches have it enabled. The History pop-up does contain that information, but since it shows the entire history of changes and not just the current values, it's not particularly user-friendly for this scenario.

Currently the best option is to create a report based on the setting name.

Revision history for this message
Andrea Neiman (aneiman) wrote :

+1, would love to see this

Changed in evergreen:
status: New → Confirmed
Revision history for this message
Jennifer Pringle (jpringle-u) wrote :

+1

This would be very handy, especially since in the angular LSE you can no longer view history for your entire consortium using the history link (in dojo a global admin could see all history, in angular it scopes based on the org unit selected).

Revision history for this message
Lindsay Stratton (lstratton) wrote :

+1

As a consortium where settings are managed centrally this is a Really Big Deal. As Terran notes, there are many cases where it is most useful to be able to quickly see all libraries' current settings at a glance. It is also useful to be able to work through a single list to update settings.

My example - I have multiple libraries that have recently changed email domains, so I am checking org.bounced_emails to make sure all libraries have been updated. Right now, a report is the only way to manage this.

Revision history for this message
Jennifer Pringle (jpringle-u) wrote :

Since we upgraded to 3.11.1 last month I've already gone back to the dojo library setting editor numerous times to look at the history for a setting to see who in our consortium has it set. (As Terran notes the old history pop-up isn't the best solution for this but it is the fastest currently.)

I'd like to propose that this bug is a blocker to fully removing the dojo interface for the library settings editor since losing the ability to see all history is a regression for global administrators.

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.