Overview
This planning has occurred in the Product Committee calls from March, April, and May of 2019 as well as on Discourse and during in-person meetings with SolDevelo in Poland during April, 2019.
...
Batch Approval - Refining the existing feature. Ability to select and process multiple requisitions. Add ability to select more than 10 requisitions (at least 80), also need to reduce the amount of data transmitted
- Epic:
Jira Legacy server System JIRA serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key MW-708 - Documentation:
- Epic:
Offline for Stock Mgmt - Stock management does not currently support offline functionality, this would include determining what to support and how.
Will the simple approach used for Requisitions work for Stock Management?
- This will likely require a deeper discussion to properly design
- Epic:
Jira Legacy server System JIRA serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-1621 - Documentation:
Demo-data - Need better data for demoing the system, currently contains a lot of automatically generated data. Would likely split the dataset into demo data and testing/performance data
- Epic:
Jira Legacy server System JIRA serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-4658 - Documentation:
- Epic:
Admin screen wizards - Configuration UI to help with the setup or update of OpenLMIS. Areas that might be improved include facility and product configuration
- Perhaps something like 'OLMIS doctor' (a la 'brew doctor') -
Jira Legacy server System JIRA serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-5124 - Epic:
Jira Legacy server System JIRA serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-5120 - Documentation:
- Perhaps something like 'OLMIS doctor' (a la 'brew doctor') -
Administrative messages - System-level messages to users (discussed in PC: April 9 2019)
- Epic:
Jira Legacy server System JIRA serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-6200 - Documentation:
- Epic:
Tracing specific products (Tracer Products)
- Epic:
- Documentation:
Cost summary in stock mgmt - Small UI change to show the overall cost summary for various stock changes
- Epics:
Jira Legacy server System JIRA serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key AO-73 Jira Legacy server System JIRA serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-5726
- Documentation:
- Epics:
Update/versioning of orderables - Ability to update the product
- Epic:
Jira Legacy server System JIRA serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-3804 - Documentation:
- Epic:
- Product Aliases - Allow searching for a product by unofficial (local) names
- Epic:
Jira Legacy server System JIRA serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-6236 - Documentation:
- Epic:
- Stock Management Performance (with Angola team) - There is a lot of low-hanging fruit here! Will have to identify which screens to focus on and create a plan for addressing all of the known performance issues
- Epic:
Jira Legacy server System JIRA serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-3814 - Documentation:
- Epic:
- Products in Multiple Programs
- Specifically for Requisitions and Reports (and Stock Management?)
- May have to consider GS1
- How would product updates work? Would they update all programs or just a single?
- Expansions to Kitting Functionality
- From the Configuration Guide: "OpenLMIS 3.0 does not currently support more advanced workflows for kits, such as: creating your own GTIN and publishing your kit via a GDSN data provider; connecting the contents inside the kit with the kit itself; tracking lots or batches once they are re-packaged inside a kit. For more about kit-related functionality that may be added in the future, see Working Notes on Products, Kits, Packaging."
- Program Data Collection
- Epic:
Jira Legacy server System JIRA serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-549 - Documentation:
- Epic:
- Offline Reporting - Generated online but accessible offline (in some form)
- Epic:
Jira Legacy server System JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key AO-40 - Documentation:
- Epic:
- Stock Management Smart Facility List
- Epic:
- Documentation:
Proposed Feature Priorities
| Feature | Priority | Size | Comments | |
|---|---|---|---|---|
| Update/Version of Orderables | High | Medium | The lack of updatable orderables results in significant time spent each month to manually process product updates for country implementations | |
| Stock Management Performance | High | The Angola team has already started working on this and it is not clear what, if anything, will need to be contributed by the core team | ||
| Admin-Screen Wizards | High | Medium | There seems to be a lot of interest from the community on this feature | |
| Administrative Messages | Medium | Small | ||
| Product Aliases | Medium | Medium | ||
| Demo Data | Medium | Large (??) | ||
| Tracer Products | Medium | Large (??) | ||
| Batch Approval | Medium | Large | ||
| Stock Management Offline | Medium | Extra Large | This is a complex task and would almost certainly be a large-sized epic. | |
| Expansions to Kitting Functionality | Medium | Large | ||
| Program Data Collection | Medium | Large (??) | Can this feature be broken down into smaller amounts of work? For specific programs? This has been identified as a key gap to be able to utilize OLMIS for certain projects. | |
| Products in Multiple Programs | ||||
| Stock Management Cost Summaries | ||||
| Administrative Messages | SmallOffline Reporting | |||
| Stock Management Smart Facility List |