|15 Sep 2020|
|Adrian Świszcz changed their profile picture.||08:41:50|
|Jimesh Shah||sbrudzinski http://172.16.7.101/test I am getting success responses for all other APIs but this API(/test) was added by me for testing purpose.||08:48:08|
|sbrudzinski||May I ask what's the URL of your development environment (the one you said it's not working) Jimesh Shah?||08:49:36|
|sbrudzinski||(edited) ... not working)? => ... not working) Jimesh Shah?||08:49:41|
In reply to@_slack_openlmis_U03QATSPZ:matrix.orgThis issue is still unsolved. You have correctly noticed that specifying the date in the program does not result in limiting the number of periods for the facility. For now, the case was described in https://openlmis.atlassian.net/browse/OLMIS-3702, and left in the Roadmap.
In reply to@_slack_openlmis_UB9E8UV89:matrix.orgThanks JoannaS!
In reply to@_slack_openlmis_U195RKK4G:matrix.org😱
In reply to@_slack_openlmis_U03QATSPZ:matrix.orgIf I read that issue right, the way forward is for someone to jump into the complexity and figure out what might be effected if we fix the bug, right?
In reply to@_slack_openlmis_U03QATSPZ:matrix.orgI guess, although I guess we looked into it two times already, and figured that only some reports might be using it for now
In reply to@_slack_openlmis_U195RKK4G:matrix.orgso it doesn't seem like there are any other dependencies or complications with this
In reply to@_slack_openlmis_U195RKK4G:matrix.orgseems like a very straightforward feature
|joshzamor||OpenLMIS and Demo data: do we need processing periods that go back to 2017 in the monthly schedule? Would it be a big deal to change to a more recent date (esp given aforementioned bug)?||14:21:20|
In reply to@_slack_openlmis_U195RKK4G:matrix.orgGreat. Does the team have a current practice for suggesting bumping an issues priority for consideration in the next grooming call? I so often have a conflict that I can't make it.
In reply to@_slack_openlmis_U03QATSPZ:matrix.orgYes, we could do that. Is it time sensitive? Because we are pretty much approaching code freeze (last sprint before regression starts)
|sbrudzinski||Some test cases might need to be updated, as well as automated functional/contract tests with this change||14:29:08|
In reply to@_slack_openlmis_U195RKK4G:matrix.orgNot that sensitive I don't think. It'd help me to have it down now of course, but that's not even a question. I'd put it in the mix for upcoming backlog grooming's though.
|16 Sep 2020|
In reply to@_slack_openlmis_U03QATSPZ:matrix.orgOkies, in that case I can bring it up after the release
|17 Sep 2020|
|@lita:synod.im left the room.||00:20:19|
|22 Sep 2020|
|Adrian Świszcz|| |
In reply to@_slack_openlmis_U03QATSPZ:matrix.orgHi joshzamor, Could you send me an invitation for today's tech committee meeting?
In reply to@_slack_openlmis_U011A2HETHN:matrix.orgYou should have it now Adrian Świszcz.
|Adrian Świszcz|| |
In reply to@_slack_openlmis_U03QATSPZ:matrix.orgThank you!
|24 Sep 2020|
|Sneha Gohel||hi @room do we have mobile app?||05:20:27|
In reply to@_slack_openlmis_U017Q6UN4R2:matrix.orgUnfortunately, no.
|Sneha Gohel|| |
In reply to@_slack_openlmis_U1GKV2T18:matrix.orgoh ok
|Damian Kryger joined the room.||09:00:48|
|Damian Kryger changed their display name from _slack_openlmis_U01BP6799CZ to Damian Kryger.||09:27:41|
|Wes||Sneha Gohel There are some mobile solutions that do leverage OpenLMIS, OpenSRP being the primary one (depending on your needs)||14:53:39|
In reply to@_slack_openlmis_UBB6KN8JJ:matrix.orgHowever, it is something that we would LOVE to have the time/funding to be able to build