Goal:Squash bugs for the To prepare for a 3.2.1 release . Judiciously continue with F&E features and performance improvements.
Grooming Question: There have been discussions around modifying the release process this time. I'd like to make sure we are clearly communicating the plan to the team. Brandon Bowersox-Johnson do you have an update from the conversations with Josh Zamor?
UPDATE: No decisions yet about the 'release candidate' process or doing a 'slow down and go careful' release for 3.2.1. So for now we are grooming priorities on this page for a squash-bug-and-release scenario, but that could change before sprint 36 begins.
Issue: Malawi faces time-outs when configurations are incorrect. Is there a way to provide an error versus timing out? See the recent slack exchange here
BUGS
There are a lot of bugs. I'm still reviewing and prioritizing. Please let me know which are top priority for you and what the impact of the bug is.
...
candidate at the end of October (~Oct 25 2017). See Release Candidate Process. Team ILL will focus on Performance. Team Parrot will focus on fixing bugs and the MUST tickets until performance tickets are available. BUGS are in priority order in the backlog.
Bugs
Go to backlog, they are in priority order (and there are 17 of them).
Image Added
These two bugs in the backlog are assigned to Team ILL
How do we want to approach this ticket? If we do a check before rejecting and then reject the requisition someone can still initiate a requisition in between.
There is no mockup.
Should it be only warning or should the newer requisition be deleted when we click the reject?
Maybe performance improvement would be to create/update rows in one database request?
F&E
Jira Legacy
server
JIRA (openlmis.atlassian.net)
serverId
448ba138-230b-3f91-a83e-16e7db1deed1
key
OLMIS-3144
Jira Legacy
server
JIRA (openlmis.atlassian.net)
serverId
448ba138-230b-3f91-a83e-16e7db1deed1
key
OLMIS-3167
Reference Data
396
(MUST)
How many values do we want to include in the CSV file for performance testing?
It is highly unlikely that this endpoint will work in less than 0.5 s as every item has to be parsed.
What is configure ISA page? Is it the page with upload export?
Stock Management
Jira Legacy
server
JIRA (openlmis.atlassian.net)
serverId
448ba138-230b-3f91-a83e-16e7db1deed1
key
OLMIS-3126
Batch Requisition
3246
(MUST)
Ticket for creating more demo data (maybe for Team ILL)
(Core team to continue looking into and figure out a plan of action)Team ILL - Sam to work with Chongsun and Josh on questions in this ticket before it can be worked on)
Ben Leibert and Christine Lenihan, please make sure the following tickets are in priority order so that we can review for the next backlog grooming call on . If bugs come in after that, please make sure to flag prior to so we can review prior to planning.Mary Jo pasted the following from sprint 35. Please delete or prioritize.
Jira Legacy
server
JIRA (openlmis.atlassian.net)
serverId
448ba138-230b-3f91-a83e-16e7db1deed1
key
OLMIS-3147
(MJ/Ben to speak with Malawi team to see if we can get more information on the desired state or willingness to use workarounds like send emails to spamcan simply set up email rules for now.)
Jira Legacy
server
JIRA (openlmis.atlassian.net)
serverId
448ba138-230b-3f91-a83e-16e7db1deed1
key
MALAWISUP
OLMIS-
128
2829
(also identified for the gap analysis) unskipping a period
Jira Legacy
server
JIRA (openlmis.atlassian.net)
serverId
448ba138-230b-3f91-a83e-16e7db1deed1
key
OLMIS-3157
(Did Malawi fork this page? Could the team check the APIs? Malawi will check the APIs)
Jira Legacy
server
JIRA (openlmis.atlassian.net)
serverId
448ba138-230b-3f91-a83e-16e7db1deed1
key
OLMIS-2829
(Not urgent, but perhaps worth mentioning so it isn't forgotten.)Not urgent, but perhaps worth mentioning so it isn't forgotten.)
Goal: Squash bugs for the 3.2.1 release. Judiciously continue with F&E features and performance improvements.
Grooming Question: There have been discussions around modifying the release process this time. I'd like to make sure we are clearly communicating the plan to the team. Brandon Bowersox-Johnson do you have an update from the conversations with Josh Zamor?
UPDATE: No decisions yet about the 'release candidate' process or doing a 'slow down and go careful' release for 3.2.1. So for now we are grooming priorities on this page for a squash-bug-and-release scenario, but that could change before sprint 36 begins.
Issue: Malawi faces time-outs when configurations are incorrect. Is there a way to provide an error versus timing out? See the recent slack ex