Epic: OLMIS-751 - Getting issue details... STATUS

OLMIS-752 - Getting issue details... STATUS - a boolean field indicating whether a program should display non fully supply fields was added. This should be used on the UI.

OLMIS-386 - Getting issue details... STATUS - saving and editing requisition templates. Templates are unique per program.

OLMIS-755 - Getting issue details... STATUS - creating periods related to schedules is possible. Validation is present.

OLMIS-230 - Getting issue details... STATUS - changing name is possible through updates. Currently there is no dependency on the name anywhere.]

OLMIS-388 - Getting issue details... STATUS - requisition template columns have an order field. Displaying in an ordered manner is left to the UI.

OLMIS-422 - Getting issue details... STATUS - Schedules can be created and updated. Schedules are currently not associated with programs!
There exists an entity mapping a schedule to a program, but it is not used for any validations etc.

OLMIS-813 - Getting issue details... STATUS - currently this is only a field in the requisition line.
The acceptance criteria should be reviewed.

OLMIS-214 - Getting issue details... STATUS - A non full supply attribute has been added to programs. No calculations were done as part of this ticket, as they are not mentioned in the acceptance criteria. Is this covered by a different ticket?

OLMIS-774 - Getting issue details... STATUS  - Skippable flag is added to a program.
Currently we have no period validation when creating a requisition.

OLMIS-786 - Getting issue details... STATUS - A column of the requisition template can be mark as displayed/non-displayed

OLMIS-811 - Getting issue details... STATUS - Attributes marking a column as non-movable have been. However the program columns itself hasn't been added - we need a ticket which will encompass adding the predefined columns and their calculations.

OLMIS-810 - Getting issue details... STATUS   - Same as above

OLMIS-812 - Getting issue details... STATUS - Beginning balance was added and is calculated, but currently is not directly tied to the requisition template, since we are missing predefined columns.

OLMIS-817 - Getting issue details... STATUS - Names can be edited

Epic:  OLMIS-575 - Getting issue details... STATUS

OLMIS-770 - Getting issue details... STATUS - Saving basic requisitions is possible. As mentioned previously there is no validation check for periods when creating a requisition. Make sure the SDR edit is properly translated to MVC edit.

OLMIS-219 - Getting issue details... STATUS - Deleting was implemented and only initiated requisitions can be deleted.

OLMIS-218 - Getting issue details... STATUS - Done similar to v2 - you create a requisition with a skipped status. There might be a better solution however. Investigate!

OLMIS-760 - Getting issue details... STATUS  -
A requisition object can be created through the API with the initiated status. This is just creating a basic object and tying with the mentioned fields. The template does not come in to play here.

OLMIS-741 - Getting issue details... STATUS - Stock on hand is not calculated. 

OLMIS-807 - Getting issue details... STATUS - The field "requested quantity" is required

Template - missing letters representations (can be done on UI??). Missing calculation formulas and calculation logic.

Epic OLMIS-747 - Getting issue details... STATUS

OLMIS-226 - Getting issue details... STATUS - Converting to orders is done. Order file is generated during the print action. Status check on the requisition is missing.

OLMIS-224 - Getting issue details... STATUS  - Requisitions can be rejected and go back to initiated status. Only authorized requisitions can be rejected here. RBAC and audit log is not present. 

Epic OLMIS-744 - Getting issue details... STATUS

OLMIS-773 - Getting issue details... STATUS  - skipping is currently configured as a global variable. When it is configured, it's possible to approve an unauthorized requisition. There is a disrepancy between checks in reject/approve requisition - approve does not take this into consideration. We should switch this to the save phase (set status to authorized during submit), instead of doing this on the read phase.

OLMIS-229 - Getting issue details... STATUS - and endpoint for searching trough requisitions has been added. It allows searching as described in the acceptance criteria.

OLMIS-642 - Getting issue details... STATUS - authorize and approve seem to be  mixed up in the acceptance, it should be re-checked. Authorizing is done and changes status from submitted to authorized. Rbac and audit log are not present.