...
- Showcase 3 new features - UI and Requisition
- (1) Offline requisition form - form fill-out, not initiation or approval
- (2) Emergency requisitions - working in UI
- (3) My Supervised Facilities requisitions - working in UI
- Order Service - API
- Split orders into an independent service (1314)
- Goal: After this sprint, a team is ready to work in parallel on significant orders features (to discuss at Monday Sprint 13 Q&A meeting)
- Bugs
- 13 bugs from list below
- Extension Modules
- publishing to Maven and being able to deploy an extended service
- stretch goal is starting the extending data tooling (Team ILL)
...
More template fields (933 Total Cost, 1134)Requisition Improvements epicComments - 1063?
...
Remember, we aren't requiring that all 4 of these go into sprint 13 — please only pull in as much work as we can finish in this sprint, but please pull items into the sprint in this priority order. It would be great if you play planning poker on all of these tickets and add story points to them, but then only pull into your sprint what can fit. And keep in mind this sprint is 2 days shorter.
1. Showcase 3 new features - UI and Requisition
...
- Offline (1038, 1338, 1339)
- Non-full products (it was a roll-over)
- Emergency Requisitions (roll-over)
- My Supervised Facilities (roll-over and 1315)
- UI Inventory clean-up (1358, 1343)
- User profile page (roll-over)
- Documentation/NGDoc (______OLMIS-1280)
Wait on 1349.
Jira Legacy | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
Finish requisitions (skip, comments?, print)Potentially look into doing the configuration screen for the requisition template
Order Export
We will split the Order Service in Sprint 13. After that, we will be ready to do rounds of new Order functionality in sprint 14 and a few sprints beyond.
...
For Sprint 13, do the bugs in the table below EXCEPT: 1119, 130 (which is not for v3), and not the ones already in the Team ILL sprint (1074).
+
Jira Legacy | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
---------------------------------------------------------------------------------------------------------------------
...
|
Jira Legacy | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
Requisitions - WAIT ON THESE
Advanced Template: ranking is not accurate but all need to be estimated.
Jira Legacy | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
Improvements: ranking is not accurate but all need to be estimated.
WAIT on all these. WAIT on 1102 and 536 and 1009.
Questions:
Jira Legacy server JIRA (openlmis.atlassian.net)
...
...
serverId 448ba138-230b-3f91-a83e-16e7db1deed1
...
- no idea what this is aboutkey OLMIS-1358 Jira Legacy server JIRA (openlmis.atlassian.net)
...
...
serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key
Potential other tickets - WAIT ON ALL THESE
...
- not clear, are we removing validation that triggers after editing the inputs in this ticket? What exactly should be done?OLMIS-1348 Jira Legacy server JIRA (openlmis.atlassian.net)
...
...
- why is this necessary? in order to minimize the manifest?serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-1341