| Target release | Release name or number |
|---|---|
| Epic | Reporting - Order cost |
| Document status | |
| Priority | |
| eLMIS Status | Implemented |
| OpenLMIS Status | Not implemented |
| PATH | |
| OpenLMIS | Mary Jo Kochendorfer (Deactivated) |
| JSI | Ashraf Islam (Unlicensed) |
|
Displays cost estimation of approved requisition
Status in eLMIS: Implemented.
Status in OpenLMIS: Not implemented
Priority: High priority for Tanzania
Use:
The report shows:
Note: PDF and Excel export includes addional datapoint Supplimental Funds Used
Parameters:
In this story user means or one of the following, Health Facility incharge, DMO, Community and Regional Management Team (C/RHMT), Logistics officer/Advisors, Senior level decision maker, M&E officer/Advisor etc
| # | Title | User Story | Label | Importance | Notes | JIRA Tickets |
|---|---|---|---|---|---|---|
| 1 | Export reports to Excel | As a user, I need to be able to export all reports and analysis reporting results into Excel so that I can process the data more and analyze it in Excel. | Reports | Must have for TZ | ||
| 2 | Print reports with headings and logs | As a user, I need to be able to print reports with customized headings and logos so that I can file the report for future references. | Reports | Must have for TZ | ||
| 3 | View order cost | As a user, I need to be able view how much it would cost to place order | Reports | Must have for TZ | ||
| 4 | View line number for items in product list | As a user, I want to see a number for each row in the product list returned so that I can easily see how many items were returned. | Reports | Must have for TZ | ||
Include any business process mapping, mockups, diagrams or visual designs relating to these requirements. Describes the tasks and the personas who perform those activities. The diagram provides the context for the user stories and serves as a focal point for achieving clarity and agreement among stakeholders. Looks like a standard flow chart.
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 |
|---|---|
| Name of story or release | Link to JIRA |
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 |