Backlog Grooming Sprint 18

Owned by Mary Jo Kochendorfer (Deactivated)
Last updated: Jan 25, 2017 by Sebastian Brudziński
1 min read

Themes:

  • Requisition printing, comments and column definitions.
  • UI: Offline, orders, pagination and remaining functionality


Requisitions (template and improvements)

Tickets

Printing

Comments/Status Message

Column definitions  

These are new features, and don't exist in 2.0 — Ask if you have any questions

  • OLMIS-1503 - Getting issue details... STATUS
  • OLMIS-1501 - Getting issue details... STATUS  (UI) - blocked, not picked up
  • OLMIS-1502 - Getting issue details... STATUS  (UI)

Stretch/Sprint 19

  • Later (maybe after 3.0 or not happening at all): OOD Refactor tickets
  • OLMIS-1627 - Getting issue details... STATUS

Fulfillment

We encourage the fulfillment team to help out on the Requisition team if these are completed.

UI

New Features

Offline requisitions 

Requisitions

General

  • OLMIS-1691 - Getting issue details... STATUS  (ILL) (Stub)
  • OLMIS-1693 - Getting issue details... STATUS  (ILL) (Stub)
  • OLMIS-1642 - Getting issue details... STATUS  (ILL) (Stub)
  • OLMIS-1692 - Getting issue details... STATUS  (ILL) (Stub)
  • OLMIS-1661 - Getting issue details... STATUS  (Stub)
  • OLMIS-1354 - Getting issue details... STATUS
  • OLMIS-1025 - Getting issue details... STATUS  (Stub)

Orders

  • OLMIS-1550 - Getting issue details... STATUS
  • OLMIS-1566 - Getting issue details... STATUS  (Stub & Might change to merge with   OLMIS-1549 - Getting issue details... STATUS )

Changes:

Bugs from demo data (maybe)

  • OLMIS-1580 - Getting issue details... STATUS  (needs to be reproduced)
  • OLMIS-1581 - Getting issue details... STATUS  (needs to be reproduced)
  • OLMIS-1576 - Getting issue details... STATUS  (Related to OLMIS-1409)

Transifex string cleanup

(Mary Jo Kochendorfer (Deactivated) wants to work on these)


Stretch/Sprint 19

  • OLMIS-1682 - Getting issue details... STATUS (do we implement all the options presented in the description? It seems like we have a choice to provide the template as a markup directly or as a link to the file)
  • OLMIS-1603 - Getting issue details... STATUS  (STUB: waiting for feedback)
  • OLMIS-1481 - Getting issue details... STATUS  (Stub)
  • OLMIS-1535 - Getting issue details... STATUS   STUB (Update message string to be one string and change text) Potentially 19
  • OLMIS-1538 - Getting issue details... STATUS  STUB (needs clean up – ie add error message)
  • OLMIS-1543 - Getting issue details... STATUS  Needs to be reproduced
  • OLMIS-1448 - Getting issue details... STATUS (do we need this in 3.0? Will we have any select inputs where we want this? This is yet another custom solution we want to implement)
  • OLMIS-403 - Getting issue details... STATUS  (Needs checkin)

Reporting

Reference Data

Stretch:

  • OLMIS-1444 - Getting issue details... STATUS  (for Team ILL)

  • OLMIS-1696 - Getting issue details... STATUS (for Team ILL)
  • OLMIS-1695 - Getting issue details... STATUS (for Team ILL)

Auth

  • OLMIS-1598 - Getting issue details... STATUS  Important for 3.0
  • Stretch goal:  OLMIS-1626 - Getting issue details... STATUS

Platform



Stretch:

QA

OpenLMIS: the global initiative for powerful LMIS software