View Orders has broken requesting facility filter select
Description
The View Orders page has a "Requesting Facility" filter select dropdown, but it never has any options to select. Actually, as "admin" you have choices but as wclerk2 or wclerk1 the field never has options. There appears to be legitimate data with orders that have a requesting facility, but no facilities can be selected on the dropdown (unless user is admin).
This is not a show-stopper bug, because users can work around it by just paginating through the orders or using the other filters on the left to shorten the list. They just cannot filter by facility.
Steps to Reproduce
Reproduced on Chrome on Test server today (confirmed it also happens on Demo server, so the bug has been there since 3.1.0 and perhaps earlier).
Log in as wclerk1 (which has rights to view orders and there are 2 orders in the demo data)
Navigate to Orders > View Orders
ERROR: The Facility dropdown on the left has no options to select. See screenshot.
Environment
Activity
The UI will compile the final list of available requesting facilities based on the endpoint call and the cached data it has got. It will call the endpoint in the fulfillment service to retrieve UUIDs of all available requesting facilities, check the facilities cache to match those UUIDs with names and then display the available requesting facilities to the user. Since the search order endpoint already supports filtering by requesting facility UUID, no further changes are required there.
Who is taking on the work of linking the cached facilities to the view orders page? Do we need another ticket for this?
Hey . We will be adjusting this dropdown as a part of this ticket.
FYI, there is some talk in ticket of a way that the Facility dropdowns and Program dropdowns can be powered by shared components with different rights checks applied for different parts of the OpenLMIS UI. Please take a quick look at that ticket and feel free to ask Mateusz or Paweł if you have questions.
, will this ticket be done for the release today?
I just moved it to QA and check it on Malawi dev server. Now we are waiting for Core team approval.
Assignee
Reporter
Labels
Story Points
Time tracking
Time remaining
Components
Sprint
Fix versions
Priority
