...
| Jira Legacy |
|---|
| server | JIRA (openlmis.atlassian.net) |
|---|
| serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
|---|
| key | OLMIS-2609 |
|---|
|
| Jira Legacy |
|---|
| server | JIRA (openlmis.atlassian.net) |
|---|
| serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
|---|
| key | OLMIS-2604 |
|---|
|
| Jira Legacy |
|---|
| server | JIRA (openlmis.atlassian.net) |
|---|
| serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
|---|
| key | OLMIS-26182790 |
|---|
|
(if we don't want to start on the inventory we could continue to build out catalog tickets)needs investigation)
Nice to have
| Jira Legacy |
|---|
| server | JIRA (openlmis.atlassian.net) |
|---|
| serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
|---|
| key | OLMIS-27902618 |
|---|
|
(if we don't want to start on the inventory we could continue to build out catalog tickets)
Q: Paweł Gesek ILL would like to try making showcase videos for the above CCE tickets (OLMIS-2609 & 2618) – please comment if you agree.
...
| 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-2715 |
|---|
|
| 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-2747 |
|---|
|
| Jira Legacy |
|---|
| server | JIRA (openlmis.atlassian.net) |
|---|
| serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
|---|
| key | OLMIS-2517 |
|---|
|
| Jira Legacy |
|---|
| server | JIRA (openlmis.atlassian.net) |
|---|
| serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
|---|
| key | OLMIS-2797 |
|---|
|
(ILL)
- Need to set correct behavior – assume field errors only show after user leaves cell (could also show errors as user leaves row, or tries to change page)
Nice to have
Fulfillment
| 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-2724 |
|---|
|
| 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-2726 |
|---|
|
| Jira Legacy |
|---|
| server | JIRA (openlmis.atlassian.net) |
|---|
| serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
|---|
| key | OLMIS-2781 |
|---|
|
- (based on discussion in PR #4 — Paweł Gesek has reviewed the issues there and has a suggestion for how we move forward: his suggestion is to remove the GET /api/orders endpoint entirely. This "get all orders" endpoint is not used by the UI or anyone as far as we know. Instead everyone will use the /api/orders/search endpoint to find a specific set of orders returning a list of order UUIDs. Pawel also believes the GET /api/orders is not in v2, it was only created in v3 but never used. Josh Zamor do you agree?
- Paweł Gesek, please see latests guidance in OLMIS-2781
Reference UI
| Jira Legacy |
|---|
| server | JIRA (openlmis.atlassian.net) |
|---|
| serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
|---|
| key | OLMIS-2661 |
|---|
|
(Team ILL)| Jira Legacy |
|---|
| server | JIRA (openlmis.atlassian.net) |
|---|
| serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
|---|
| key | OLMIS-2146 |
|---|
|
(Team ILL)| Jira Legacy |
|---|
| server | JIRA (openlmis.atlassian.net) |
|---|
| serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
|---|
| key | OLMIS-2798 |
|---|
|
| Jira Legacy |
|---|
| server | JIRA (openlmis.atlassian.net) |
|---|
| serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
|---|
| key | OLMIS-2738 |
|---|
|
(needs to be reproduced)| 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-2714 |
|---|
|
(Needs to be reproduced — also needs review to see if general bug and 'global' approach can be taken)| Jira Legacy |
|---|
| server | JIRA (openlmis.atlassian.net) |
|---|
| serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
|---|
| key | OLMIS-2655 |
|---|
|
| Jira Legacy |
|---|
| server | JIRA (openlmis.atlassian.net) |
|---|
| serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
|---|
| key | OLMIS-2805 |
|---|
|
| Jira Legacy |
|---|
| server | JIRA (openlmis.atlassian.net) |
|---|
| serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
|---|
| key | OLMIS-2803 |
|---|
|
- The remaining work here is centering the modal (and actually all modals)
- There is a discussion about how center we want these modals to be (generally off center looks right)
- Ideally the modals would adjust based on the screen height
| Jira Legacy |
|---|
| server | JIRA (openlmis.atlassian.net) |
|---|
| serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
|---|
| key | MW-348 |
|---|
|
Login needs loading modal (bring in from MW-UI)
...