Allow requisition submitters to more readily view their pending requisitions

Description

Several types of users might generically be thought of as “requisition submitters.” Each of them is refereed to within a story below.

Story #1

As a storeroom clerk potentially working at multiple facilities, I’d like a convenient way of reviewing all requisitions I’ve submitted but which have not yet been authorized. This will help me recall what’s been requested and potentially reach out to the person responsible for servicing the requests in the event of a delay.

Story #2

As a storeroom manager potentially responsible for multiple facilities, I’d like a convenient way of reviewing all requisitions I’ve authorized but which have not yet been approved. This will help me recall what’s been requested and potentially reach out to the person responsible for servicing the requests in the event of a delay.

Story #3

As a district storeroom manager, I’d like a convenient way of reviewing all requisitions I’ve approved but which have not yet been converted into an order. This will help me recall what’s been requested and potentially reach out to the person responsible for servicing the requests in the event of a delay.

I don’t imagine that storeroom clerks/managers often work at multiple facilities, but am under the impression it happens. In such cases, the requirement that a single facility is specified on the Requisitions -> View page hinders the user’s ability to see all of their requisitions awaiting someone else’s response.

Potential quick/easy fixes include:

  • Making the choice of a facility on the Requisitions -> View page optional. Casual testing in Malawi’s environment suggests that paginated requests unfiltered by facility would take around 70 seconds to return.

  • Making the choice of a facility on the Requisitions -> View page optional but, in order to allow for more performant requests, adding an optional Program dropdown. Casual testing suggests that this would significantly reduce response times. The new Program dropdown would supplement rather than obviate the existing Program filter (which effects what’s displayed on the UI but not what’s requested of the backend.)

The results offered by either of the above two options could alternatively be achieved by a report. This approach, though, may take more effort and encounter similar performance issues.

Assignee

Unassigned

Reporter

Ben Leibert

Labels

None

Components

Affects versions

Priority

Minor
Configure