...
| THINGS TO DO (not sure which team yet) |
|
|---|
performance - get data to make decisions
- (plus more in Platform)
| performance: - OLMIS-3073 (the follow-up ticket)
- OLMIS-2912
|
| Batch Requisition view feature | UI improvements: - improved tabing
- oh snap error
|
| sort controls | order number extension point/configurability |
| admin screen (1 per sprint) |
|
|
|
Bugs
| Jira Legacy |
|---|
| server | JIRA (openlmis.atlassian.net) |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
|---|
| key | OLMIS-3083 |
|---|
|
| Jira Legacy |
|---|
| server | JIRA (openlmis.atlassian.net) |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
|---|
| key | OLMIS-3076 |
|---|
|
(Team ILL - Brandon, Mary Jo, and Sam need to document the process for this first)| Jira Legacy |
|---|
| server | JIRA (openlmis.atlassian.net) |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
|---|
| key | OLMIS-2903 |
|---|
|
...
| Jira Legacy |
|---|
| server | JIRA (openlmis.atlassian.net) |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
|---|
| key | OLMIS-2857 |
|---|
|
| Jira Legacy |
|---|
| server | JIRA (openlmis.atlassian.net) |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
|---|
| key | OLMIS-2758 |
|---|
|
| Jira Legacy |
|---|
| server | JIRA (openlmis.atlassian.net) |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
|---|
| key | OLMIS-2283 |
|---|
|
Forecast and Estimation
Can/should we start on F&E tickets? Perhaps we aim to get this groomed by Chongsun Ahn (Unlicensed) or Josh Zamor in this sprint? Goal is to have ticket acceptance criteria updated in this sprint, not completion of the tickets.
| Jira Legacy |
|---|
| server | JIRA (openlmis.atlassian.net) |
|---|
| serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
|---|
| key | OLMIS-2966 |
|---|
|
| Jira Legacy |
|---|
| server | JIRA (openlmis.atlassian.net) |
|---|
| serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
|---|
| key | OLMIS-396 |
|---|
|
(Shall we break this up or not?)| Jira Legacy |
|---|
| server | JIRA (openlmis.atlassian.net) |
|---|
| serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
|---|
| key | OLMIS-2892 |
|---|
|
Requisition
| Jira Legacy |
|---|
| server | JIRA (openlmis.atlassian.net) |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
|---|
| key | OLMIS-3072 |
|---|
|
(Team ILL)
...
| Jira Legacy |
|---|
| server | JIRA (openlmis.atlassian.net) |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
|---|
| key | OLMIS-3108 |
|---|
|
| Jira Legacy |
|---|
| server | JIRA (openlmis.atlassian.net) |
|---|
| serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
|---|
| key | OLMIS-2956 |
|---|
|
| Jira Legacy |
|---|
| server | JIRA (openlmis.atlassian.net) |
|---|
| serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
|---|
| key | OLMIS-2655 |
|---|
|
(Needs a component approach here; TBD whether this is Team ILL or Parrot)| Jira Legacy |
|---|
| server | JIRA (openlmis.atlassian.net) |
|---|
| serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
|---|
| key | OLMIS-3097 |
|---|
|
(Team ILL needs to define this ticket and make sure we have MW buy-in)
...
- )
| Jira Legacy |
|---|
| server | JIRA (openlmis.atlassian.net) |
|---|
| serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
|---|
| key | OLMIS-3114 |
|---|
|
(Team Malawi requests core support on this)| Jira Legacy |
|---|
| server | JIRA (openlmis.atlassian.net) |
|---|
| serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
|---|
| key | OLMIS-3115 |
|---|
|
(Team Malawi requests core support on this)
Reporting
Reference Data
| Jira Legacy |
|---|
| server | JIRA (openlmis.atlassian.net) |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
|---|
| key | OLMIS-3105 |
|---|
|
(Team ILL - Chongsun)| Jira Legacy |
|---|
| server | JIRA (openlmis.atlassian.net) |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
|---|
| key | OLMIS-3109 |
|---|
|
(Team ILL - Brandon)
...