Bugs
- (perhaps we can pick up this sprint?
- (wasn't picked up for 3.0.2)
- New
- (wasn't picked up for 3.0.2)
- (wasn't picked up for 3.0.2)
- (wasn't picked up for 3.0.2)
- New
- New
- New
- (wasn't picked up for 3.0.2)
- (wasn't picked up for 3.0.2)
- still more...
Requisition
Will be working towards 3.1.3-SNAPSHOT. Because requisition-3.1.2 is planned to be released end of April in ref-distro-3.0.2.
- MUST (request from Malawi)
- (UI) (wasn't picked up for 3.0.2)
- (UI) (wasn't picked up for 3.0.2)
- (UI) (wasn't picked up for 3.0.2)
Stretch Goals:
- (Do we have to do this for 3.1??)
Waiting (may be a pull request from Malawi team):- This ticket does not have the current/latest design:
Do we still need ? or ?
Reference Data
Will be working towards 5.1.0-SNAPSHOT. Because referencedata-5.0.0 is planned to be released end of April in ref-distro-3.0.2. Improvements such as 2357 make this a Minor bump to 5.1.0, not a patch 5.0.1.
- - MUST (blocks OLMIS-2322)
Start adding Audit logging for Reference data
- Users - - MUST
Admin Pages
- - MUST
- View Orderables - MUST (Sam is still adding details to story)
Question to Sam
Stretch:
- (Malawi doesn't think they'll get to this)
- Edit Facilities
Platform
- Next on Ad-hoc Reporting
Stretch:
- Improve workflow so that fixing bugs results in a new automated test
- (might need spike)
Anything around Reporting?
If program data PoC should proceed: