[API] View current Stock on Hand by Facility/Program

Description

As a storeroom manager at a location that keeps stock, I want to know how much of each product I have on hand so that I know when I need to reorder, and so that other users higher in the health system know when I'm out of stock

Scope out:
Permission management, which facility can be chosen by the end user to view the corresponding SOH;
UI;
Month of stock covered by OLMIS-924;
Search function on the UI page;
Sort function on the UI page;
Max Stock Quantity is defined in OLMIS-887;
Min Stock Quantity defined in OLMIS-978;
Navigation on the UI page (e.g. Clicking on a product displays its electronic stock card (https://openlmis.atlassian.net/browse/OLMIS-625#icft=OLMIS-625);
Lot function related stuff;

Acceptance Criteria

1. The default chosen facility is the user's home facility.

2. The API request should include facility ID, program ID and a valid access token.

3. After receiving a valid API request, the API would response back the information of all products on the approved product List and their current SOH if they have

User can select the program they want to view products' SOH for. For selected program, system displays all the products available in the program in a list, along with the current SoH for each product.If no program is selected, display all products for the selected facility

Questions/notes from story's history to consider This is the first MVP story for stock management. The UI can be throw-away, or can be used as the basis for future additions (dev decision) Group by program potentially

Looking forward

  • If lot management is "on", display SOH for the product by lots. Display expiry (Need to discuss UX for this)
    i.e.
    Paracetemol 120
    Lot A 75
    Lot B 45

  • Display/sort based on expiry (make this configurable)

  • Do we want the concept of "favorites" where users can save favorites and re-add products?

  • months of stock-

Attachments

1

Activity

Show:
Brandon Bowersox-Johnson
March 1, 2017 at 1:54 AM

Yes, that makes sense to me. Thanks!

Shiyu Jin
February 28, 2017 at 3:23 AM

Hey Since we are onboarding a new QA now, I would like him to QA all stories we have done for previous sprints. Thus, I would mark them all as QA status and assign them to current sprint. If we cannot finish testing them all, we can always move them to the next sprint.
Does this make sense to you?

Brandon Bowersox-Johnson
February 27, 2017 at 7:52 PM

Hey , somehow all of these 3 tickets from last sprint are marked "QA" status, but they are no longer in any sprint. They are back in the Backlog in JIRA.

I suggest our process is that tickets in QA would get moved to the next sprint (Panda Sprint 6) if they are not closed when the previous sprint (5) ends. They would still be in the QA status.

Does that process make sense? If so, please move these into Sprint 6 and assign them to the person who will QA them.

Also, on a separate note, because these Stock Management features are not shipping in Version 3.0 of OpenLMIS, I will be changing the "fixVersion" tag of many of the tickets. Let me know if you have any questions.

Shiyu Jin
February 10, 2017 at 9:48 AM

Strikethrough UI related stuff as this ticket only covers the API part.

Done
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Story Points

Components

Sprint

None

Fix versions

Priority

Time Assistant

Created March 25, 2015 at 12:13 AM
Updated February 15, 2018 at 8:03 PM
Resolved March 8, 2017 at 4:28 AM