|
<Insert background and context so people can understand why we developed the feature the way we did>
Shiyu Jin (Deactivated), please update the following table with the tickets and user story column.
Title | User Story | Label | Importance | Notes | |
---|---|---|---|---|---|
1 | [API] View current Stock on Hand by Facility/Program | Must have | API story | ||
2 | [UI] View SOH summary (currently) | Must have | UI story |
Shiyu Jin (Deactivated), please enter the final mockups and steps here so it is clear what the system is doing.
Identify initial dependencies that are on the critical path for this functionality and may affect the delivery time and serving of business goals. Include links to stories.
Description | Link |
---|---|
Make the noticed date as the sever processing time instead of front end created event time | |
Permission Management for stock management |
Initial communication between stakeholders and the development team to help understand scope and estimates.
Below is a list of questions to be addressed as a result of this requirements document:
# | Question | Outcome | Status |
---|---|---|---|
1 | Communicate the decision reached | Open, In Progress, Closed, and date of closure | |
2 |