[$250] Further QA issues

[jmgasper]

Issue 5

Issue 5: The times set are not getting saved correctly

vid5.mp4

Issue 6

Issue 6: when changing the registration time from WM(so the registration phase start time < current EST time), the fields related of other phases(except registration) gets disabled in WM. They only get enabled again when registration time is changed from WM

vid6_1.mp4

vid6_2.mp4

[maxceem]

Challenge https://www.topcoder.com/challenges/94a913e0-a4c0-4048-a93f-836575c95415 has been created for this ticket.

This is an automated message for maxceem via Topcoder X

[maxceem]

Challenge https://www.topcoder.com/challenges/94a913e0-a4c0-4048-a93f-836575c95415 has been assigned to nursoltan-s.

This is an automated message for maxceem via Topcoder X

[jmgasper]

As discussed via email, to work around the API limitations

Hmm… Maybe we only allow duration to be changed for subsequent phases?  We shouldn’t allow any “gaps” between the end of one phase and the start of the next, so it may make sense to:

1.  Allow the user to change the start date for the very first phase, before the challenge is launched
2. After the challenge is launched, they can only change the duration of phases, nothing else

We would still show the start and end point, but they wouldn’t be editable.

NOTE - we need to allow for all phases durations to be editable before the challenge starts (currently future phases are locked).

The user should be able to set the registration start date, and then the duration of all phases, before the challenge starts.

[jmgasper]

@nursoltan-s - Just checking in here, thanks!

[nursoltan-s]

@jmgasper Hi, please check this PR:
#1350

[jmgasper]

@nursoltan-s - A couple things:

1. Registration and Submission are always concurrent, but submission could have a longer duration. Their start times should always be the same though. Note that I think that the API will handle this, but the UI should as well.

2. When changing the duration of one phase, the duration of the other phases shouldn't be affected - we'll just adjust the start and end dates. For instance, in my test, I saw that changing the duration of registration affected the duration of submission and review, which shouldn't happen.

3. Can we populate the time value with the currently selected time? Right now it seems to default to 12:00AM (bumped payment since this wasn't clearly defined earlier)

[nursoltan-s]

@jmgasper
Fixed above feedbacks:
#1351

[jmgasper]

Looks good, thanks. Going to ask QA to take a look as well.