Page Comparison

...

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

...

1. Offline (1038, 1338, 1339)
2. Non-full products (it was a roll-over)
3. Emergency Requisitions (roll-over)
4. My Supervised Facilities (roll-over and 1315)
5. UI Inventory clean-up (1358, 1343)
6. User profile page (roll-over)
7. Documentation/NGDoc (______OLMIS-1280)

Wait on 1349.

• 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).

+ Contract Test for Requisition  

Questions:

• Jira Legacy
  server JIRA (openlmis.atlassian.net) serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-1358

   - no idea what this is about

• Jira Legacy
  server JIRA (openlmis.atlassian.net) serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-1348

   - not clear, are we removing validation that triggers after editing the inputs in this ticket? What exactly should be done?

• Jira Legacy
  server JIRA (openlmis.atlassian.net) serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-1341

  - why is this necessary? in order to minimize the manifest?