When I create a new processing schedule and add one processing period, I cannot add a second processing period because the modal will not let me select a Start Date.
Steps to Reproduce:
Create new processing schedule.
Add a processing period - select Start Date 4/1/2018 - 4/30/2018 and click Add. New processing period is added successfully.
Try to add a second processing period - user cannot select start date. Then select end date as 5/31/2018 then click Add. User receives an error message that the processing period cannot be added because a Start Date is not selected.
When a processing period is created, the second processing period should use ONE day following the first processing period end date. In this example, the start date for the second processing period should automatically populate as 5/1/2018.
The priority of this bug is critical because the user cannot complete a standard process.
I started testing the ticket and noticed that, unfortunately, it's not possible to add even the first processing period to processing schedules not containing any processing periods (e.g. SCH005 or a newly-created one) because it's not possible to choose the start date, the "Start Date" select is disabled. For processing schedules that have processing periods already created (e.g. SCH001), adding new processing periods works correctly.
I re-tested the ticket, and now creating processing periods works correctly. Unfortunately, I noticed two issues with other date pickers:
1. In the Facilities > Associated Programs tab, it is possible to save the changes with an incorrect value (e.g. 00/00/0000 or letters) in the "Start Date" datepicker. The exclamation mark appears but the changes are seemingly saved. Yet after returning to the tab, the input field is null.
2. The datepicker in the "Date Physical Stock Count Completed" broke. Please look at the screenshots to see what happens when invalid values are entered. Also, even when correct ones (e.g. today's date) are entered, it's impossible to submit the requisition - the "This form is invalid" modal occurs.
Also, can changes in datepickers break pagination? I'm asking about it because I noticed that a huge number of errors occurs in the console when going e.g. to the Requisition Initiate view, View Requisitions or all Stock Management screens.
No, they can not. Also I was unable to reproduce this. I have resolved other issues.
OK, thank you. After the re-deploy I can't do it either.
I made a re-test, and now everything works correctly.