...
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-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-2814 |
---|
|
- App Cache Offline Design
- Change UI Documentation to support Component Based design
- Work on tech comm UI modularity (Team ILL)
Jira Legacy |
---|
server | JIRA (openlmis.atlassian.net) |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-2030 |
---|
|
(Team ILL) Jira Legacy |
---|
server | JIRA (openlmis.atlassian.net) |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-2316 |
---|
|
(TeamILL) 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-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) |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-2716 |
---|
|
(Need additional feedback in comments from Josh Zamor before working on this.) Jira Legacy |
---|
server | JIRA (openlmis.atlassian.net) |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-2696 |
---|
|
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-2787 |
---|
|
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-2811 |
---|
|
...
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 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)
- 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.
Malawi Contributions
Team ILL and Ben Leibert and Sebastian Brudziński to figure out how to get the following features back into core.
- 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
Notes and discussion on the following:
Josh Zamor to review the following tickets and re-prioritize.
- 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)Also, we have asked component leads to upgrade Gradle and tooling versions (see https://groups.google.com/forum/#!topic/openlmis-dev/2LpkxEk5vFM). Should we use tickets to track this (so we have a consistent version used before our next release)?