Summary

Add custom request units at item level (assumes [PACKS] #0 is complete and merged, which will give us all the appropriate fields on the database and some examples in the seed)

Why

This is step #2 of adding the ability to specify "packs" versus "individual" for requests

Details

Add custom request units used to the item on edit, show, and list.

a) On item new/edit (Inventory|Items&Inventory|New Item or Edit the specific item)

Iff the bank is using customized request units:

Add a "additional custom request units (e.g. packs)" field Multi-Select additional request units, if any (from the list specified at org level)

Screenshot hint for placement

b) Item show

The item show does not currently show every field in the item, only a subset plus the levels for each storage location. We're splitting that into a separate issue (PACKS 12), as it is not crucial for release and requires a slight redesign.

c) Item list

Iff the organization is using customized request units, add a column to the list that shows the customized request units used on each item

Screenshot hit for placement

N.B.

All of the UI changes for PACKS must be implemented behind a flipper flag "enable_packs"

Criteria for completion

[ ] functionality as described above
[ ] tests that support the functionality as described above

Background

The following sections have been identified as required for the PACKS implementation. The necessary fields and seed elements are implemented in [PACKS]#0