...
| # | Title | User Story | Label | Importance | JIRA tickets | ||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Phase 0 | |||||||||||||||||||||||||||||||||
| 1 | Make stock adjustments reason specific | Phase Zero: update data models to prepare for connecting Stock and Requisition |
| ||||||||||||||||||||||||||||||
| 2 | Change Physical Inventory to include reasons for discrepancy | Phase Zero: update data models to prepare for connecting Stock and Requisition |
| ||||||||||||||||||||||||||||||
| Phase 1 | |||||||||||||||||||||||||||||||||
| 3 | Add date field to Requisition form | Phase 1: Simple connection of requisition and stock |
| ||||||||||||||||||||||||||||||
| 4 | Change Requisition adjustment reasons to come from Stock Service (including data migration) | Phase 1: Simple connection of requisition and stock |
| ||||||||||||||||||||||||||||||
| 5Requisition service requires Stock service be active | Deprecate all Adjustment Reasons endpoints in RefData | Phase 1: Simple connection of requisition and stock |
| ||||||||||||||||||||||||||||||
| 6Deprecate all Adjustment Reasons endpoints in RefData | Requisition service requires Stock service be active | Phase 1: Simple connection of requisition and stock |
| ||||||||||||||||||||||||||||||
| 7 | Requisition form info gets pushed into Stock Physical Inventory | Phase 1: Simple connection of requisition and stock |
| ||||||||||||||||||||||||||||||
| 8 | Document the simple Requisition-Stock connection | Phase 1: Simple connection of requisition and stock |
| ||||||||||||||||||||||||||||||
| Phase 2 | |||||||||||||||||||||||||||||||||
| 9 | In Requisition Template, add radio button option to choose Simple or Advanced connection to Stock service | This is a new radio button with two choices: "Requisition only" and "Connect to Stock Management". Text under the Stock Management option needs to say it is not available offline. This is a new radio button If the OpenLMIS Stock service of at least version 1.0.0-beta is installed and available at its API (check version API endpoint), then we allow the radio button to be chosen; otherwise it is disabled. Changing this radio button setting saves/persists this setting as part of the Requisition Template for this program only. Use existing API endpoints for retrieving and saving requisition template. Permissions for changing this setting are the same as for changing any of the Requisition Template. When you try to initiate a requisition with this setting enabled, the setting should be part of the Requisition object that gets initiated and sent to API consumers (e.g., so that the UI can do something special in a later ticket if this setting is set to use Stock). If later on the Stock service becomes disabled, then when you try to initiate or edit a requisition from a template that uses the stock service, the Requisition service throws an error with a helpful message and the UI displays that. (EG, "Stock service is not found. OpenLMIS Stock Management service is required by this requisition's template.") | Phase 2: Advanced Requisition-Stock connection | ||||||||||||||||||||||||||||||
| 10 | Add Advanced Adjustments modal that comes from the Stock UI | on requisitions where 'Advanced Connect to Stock Management' is selected. We want the advanced modal to actually live in the Stock UI repo. It will mostly match the design and functionality of the existing Adjustments and Issue and Receive screens in the Stock Management UI. So Requisition UI now depends on Stock UI: add that dependency programmatically or at least in the documentation, and perhaps add error checking for if stock UI does not provide/define the modal it should give a friendly error (it could mean you are using a newer Requisition UI with an older Stock UI version that is not compatible). The default date of the first adjustment will be the ending date of the period. Similar to the Stock UI existing adjustments screen, after that the default date of the new adjustment rows added in the modal will be the previous date the user had picked for the previous adjustment. The date validation checker must limit users to only picking dates within the start date-end date range of the Requisition Period for Regular Requisitions. For Emergency requisitions there is no limit (though as before, we do not expect users to enter adjustments during Emergency requisitions). The Product is pre-selected depending on the Requisition form row, so that part of the stock UI we do not need, but we do need the Lot select field to appear for any product that has one or more active Lots defined. | Phase 2: Advanced Requisition-Stock connection | ||||||||||||||||||||||||||||||
| 11 | Refactor simple adjustments modal out of Requisition UI component and into Stock UI component | Maybe—TBD. This was originally discussed when there was only going to be an Advanced version, not a simple one; at that time we planned that the Advanced UI would be owned by the Stock Management UI component. | Phase 2: Advanced Requisition-Stock connection | ||||||||||||||||||||||||||||||
| Phase 3 | |||||||||||||||||||||||||||||||||
| 12 | Prompt user to initiate requisition | Upon finishing a Physical Inventory (in Stock), prompt user to initiate a Requisition | Phase 3: Requisition pulls data from Stock Service | ||||||||||||||||||||||||||||||
| 13 | Generated Requisition / Automatic Requisition / User-friendly enhancements | When a user initiates a Requisition at a facility and program that uses OpenLMIS Stock Management to conduct regular inventories and record adjustments/transfers, then the Requisition will get filled out with a lot of helpful time-saving data based on the latest stock data. Opening and Closing balance come from stock-on-hand values as of period start and end dates. Adjustments pulls all the adjustment transactions that are currently recorded during the period start-end date range. Received quantity totals up all receipts recorded during that date range. In short, the benefit is a nearly 'automatic' requisition form is filled out for you at the end of the period, as long as you are logging transactions in stock management during the period. TBD whether this would always happen or would be a setting you can turn on/off in the program's requisition template. | Phase 3: Requisition pulls data from Stock Service | ||||||||||||||||||||||||||||||
...