...
| Jira Legacy |
|---|
| server | JIRA (openlmis.atlassian.net) |
|---|
| serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
|---|
| key | OLMIS-2045 |
|---|
|
| Jira Legacy |
|---|
| server | JIRA (openlmis.atlassian.net) |
|---|
| serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
|---|
| key | OLMIS-2066 |
|---|
|
| Jira Legacy |
|---|
| server | JIRA (openlmis.atlassian.net) |
|---|
| serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
|---|
| key | OLMIS-2164 |
|---|
|
| Jira Legacy |
|---|
| server | JIRA (openlmis.atlassian.net) |
|---|
| serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
|---|
| key | OLMIS-2165 |
|---|
|
- Migrate other modals to use OpenLMISModalService (check if has been fixed already)
...
Grooming call thinks the following isn't needed for patch release, but planning for month of April is needed
- WARNING
| Jira Legacy |
|---|
| server | JIRA (openlmis.atlassian.net) |
|---|
| serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
|---|
| key | OLMIS-2113 |
|---|
|
– Not critical for patch release – Should figure out when we need it by and work backward
(Team ILL; Brandon is willing to write up/diagram a few options and bring to a group conversation including Team Panda, Josh, Mary Jo) | Jira Legacy |
|---|
| server | JIRA (openlmis.atlassian.net) |
|---|
| serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
|---|
| key | OLMIS-2166 |
|---|
|
(any follow-up needed?)- WAIT
| Jira Legacy |
|---|
| server | JIRA (openlmis.atlassian.net) |
|---|
| serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
|---|
| key | OLMIS-1997 |
|---|
|
(we explained versioning to Tech Committee and SolDevelo, but we should update the wiki to capture it—especially that the components are semantically versioned, but the ref-distro uses milestone version numbers; and document that we prefer to coordinate working on master towards one common goal, namely the next release, in order to avoid the added effort of branching; Brandon has some paper notes and is willing to write a draft, but I believe it would really be Josh and Tech Committee that would finalize/approve) | Jira Legacy |
|---|
| server | JIRA (openlmis.atlassian.net) |
|---|
| serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
|---|
| key | OLMIS-2162 |
|---|
|
Assign to Sam | Jira Legacy |
|---|
| server | JIRA (openlmis.atlassian.net) |
|---|
| serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
|---|
| key | OLMIS-2160 |
|---|
|
Assign to Sam| Jira Legacy |
|---|
| server | JIRA (openlmis.atlassian.net) |
|---|
| serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
|---|
| key | OLMIS-2168 |
|---|
|
- Wiki Clean-up:
| Jira Legacy |
|---|
| server | JIRA (openlmis.atlassian.net) |
|---|
| serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
|---|
| key | OLMIS-2200 |
|---|
|
and | Jira Legacy |
|---|
| server | JIRA (openlmis.atlassian.net) |
|---|
| serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
|---|
| key | OLMIS-2201 |
|---|
|
(and Mary Jo and Tenly have other wiki work it may be helpful to track) - Need to discuss with Mary Jo: go back and adjust how OLMIS-1911 is implemented to be more in line with 1.x and 2.x so future migrations will be smoother (Josh and Brandon raised this)
...
-
| Jira Legacy |
|---|
| server | JIRA (openlmis.atlassian.net) |
|---|
| serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
|---|
| key | OLMIS-1498 |
|---|
|
| Jira Legacy |
|---|
| server | JIRA (openlmis.atlassian.net) |
|---|
| serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
|---|
| key | OLMIS-1693 |
|---|
|
| Jira Legacy |
|---|
| server | JIRA (openlmis.atlassian.net) |
|---|
| serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
|---|
| key | OLMIS-2164 |
|---|
|
(UI)| Jira Legacy |
|---|
| server | JIRA (openlmis.atlassian.net) |
|---|
| serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
|---|
| key | OLMIS-2165 |
|---|
|
(UI)