Time | Item | Who | Notes |
---|
10 min | 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-1987 |
---|
|
| | - Discussion about a business case that would cause SOH be negative integer
- MJ: We also need to discuss the example of issuing stock when SOH is at zero at the time of issue.
Josh's thoughts and questions: |
20 min | 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-633 |
---|
|
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-632 |
---|
|
| | - What would be the permission for the read API
- Do we need the write API for source/destination configuration
|
10 min | 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-629 |
---|
|
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-1440 |
---|
|
| | - All reasons belong to the full reason list, can we merge these two stories?
- What would be the permission for the read API
- Do we need the write API for source/destination configuration
|
20 min | Open questions | | |
5 min | New QA onboard | | - Onboard materials for QA?
- Any defined QA process/test process we should follow?
|