...
| 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-2812 |
|---|
|
- Josh(IJosh| 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-2813 |
|---|
|
- Josh- fix pipeline views (only CCE seems to be working)
| 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-2815 |
|---|
|
- Paweł Gesek, please ask the leads to do this → upgrade Gradle and tooling versions (see https://groups.google.com/forum/#!topic/openlmis-dev/2LpkxEk5vFM). If everything goes to hell, please let us know so we can discuss.
...
- Report Service
- Performance work
- Batch approval
- blocked by refactor work in the requisition service
- Login page
- Nick Reid (Deactivated) to add a list of UI related ones
...
Josh Zamor to review the following tickets and re-prioritize notes.
- Add ticket(s) for Next Step on Performance Benchmarking and performance fixes. Can we take the MW team results from OLMIS-2701 and turn it into a wiki page with a standard suite of tests we can periodically benchmark against? Mary Jo created a Non-Functional wiki page where we should clarify our non-functionality performance goals/standards. Also, MW team has specifically identified MW-366 and MW-367 to fix. (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-2147 |
|---|
|
(Josh Zamor to move to todo after AC check?) (is this or | 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-2611 |
|---|
|
a dupe of | 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-1689 |
|---|
|
i.e. could we dead the latter)| 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-2627 |
|---|
|
(Paweł Gesek Please read this ticket and let us know if you think it's feasible and how you would approach it; it would likely need guidance or involvement from you)| 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-1329 |
|---|
|
(Josh Zamor to check AC)| 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-1509 |
|---|
|
(Josh Zamor to update AC - ODK developers would find this useful)