Backlog Grooming Sprint 13

Theme

Remember that there are roll-over tickets from Sprint 12. We ask that Teams AYIC/TOP do planning poker for the items on this grooming list, BUT only pull an amount of tickets into the sprint based on an amount of work and story points that you are confident that you can commit to finishing this sprint and showcasing on 23 November, 2016. (For comparison in Sprint 12 AYIC/TOP took on ~220 story points, but only finished ~110).

1. Showcase 3 new features - UI and Requisition
   1. (1) Offline requisition form - form fill-out, not initiation or approval
   2. (2) Emergency requisitions - working in UI
   3. (3) My Supervised Facilities requisitions - working in UI
2. Order Service - API
   1. Split orders into an independent service (1314)
   2. 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)
3. Bugs
   1. 13 bugs from list below
4. Extension Modules
   1. publishing to Maven and being able to deploy an extended service
   2. stretch goal is starting the extending data tooling (Team ILL)

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

Priorities in Order:

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.

OLMIS-1314 - Getting issue details... STATUS

Bugs

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

+  OLMIS-1330 - Getting issue details... STATUS

Questions:

• OLMIS-1358 - Getting issue details... STATUS  - no idea what this is about
• OLMIS-1348 - Getting issue details... STATUS  - not clear, are we removing validation that triggers after editing the inputs in this ticket? What exactly should be done?
• OLMIS-1341 - Getting issue details... STATUS - why is this necessary? in order to minimize the manifest?