Address requisition service design issues
Description
relates to
Sebastian Brudziński
Sebastian Brudziński
Sebastian Brudziński
Chongsun AhnSebastian BrudzińskiQAlity Plus - Test Management
Checklists
Activity
Josh Zamor
Linked in a few more stories from the doc for completeness. Moving to done.
This looks great, thanks @Brandon Bowersox-Johnson
Josh Zamor
Linking to https://openlmis.atlassian.net/browse/OLMIS-882#icft=OLMIS-882 out of the discussion in the Security and Supervision sections
Josh Zamor
linked to olmis-1063 for it to address how comments should work
Brandon Bowersox-Johnson
@Josh Zamor I'm moving this to In Review. I have filed tickets for everything in the Google Doc and linked them to this ticket. I believe this ticket (1081) is therefore Done.
During your review, please check whether the issues you raised about Security and Supervisory Nodes are adequately addressed. It looks like Chongsun addressed all of this in OLMIS-545, and it's all marked Done now. But please make sure you're satisfied that what you wrote in the google doc about that is addressed.
Josh Zamor
@Paweł Gesek, I've gone through your initial comments, responded to some, etc. Thanks.
I think the next step is to get on a call, step through each item, write tickets and prioritize for beta. I've done a pass for that call and added comments for some of the ones we shouldn't need for Beta.
Invite to follow.
Details
Assignee
Josh ZamorReporter
Brandon Bowersox-JohnsonSprint
Fix versions
Priority
MajorTime Assistant
Take Josh's analysis and break it down into tasks that we prioritize. (EG, we will need to make a ticket for the Requisition API Line Items data to return the correct columns that have been configured in the requisition template)
This ticket will likely be a group meeting that results in next steps.
The analysis: https://docs.google.com/document/d/1jlG9mmlts9K8lAXCpOuuxhkost1agOVqxCOx9oxJJHk/edit?usp=sharing