We're updating the issue view to help you get more done. 

Scheduling series of captures causes conflicts where none exists due to daylight savings miscalculation

Steps to reproduce

Steps to reproduce:
1. Schedule a series of captures on a capture agent for Class A for TuTh 12:37p for 1h 35m from Feb 2nd - May 11th
2a. Attempt to schedule a series of capture on a capture agent for Class B for TuTh 11:07p for 1h 25m from Feb 6 - May 11th

--error - conflict with captures for Class A, but only for classes from March 13th onwards

A quick test shows that if I set the duration to 25m (thereby ending at 11:32p), the error goes away

2b. Attempt to schedule a series of capture on a capture agent for Class B for TuTH starting at 2p (which should conflict with Class A) from Feb 6 - May 11th

--error - conflict only with captures for Anthro 1, but only for classes before March 13th

2c. Scheduling these courses individually (not as a series) appears to work without error

This looks like an issue with daylight savings time as the date of daylight saving change is March 11th.

Expected Results:

No conflicts at all for 2a) and conflicts for all recordings for 2b.

Workaround (if any):

You could schedule all post daylight saving captures individually, but I can't say this is really feasible for an admin to do...

Note: currently untested in 1.3, but I did not see a fix for this issue in the MH Jira, so there is a good chance that this bug is still around. If possible, please confirm this issue on 1.3.

Status

Assignee

Micah Sutton

Reporter

Kevin K Chan

Severity

Incorrectly Functioning Without Workaround

Tags (folksonomy)

None

Components

Fix versions

Affects versions

1.2.x (branch)
1.3
1.2

Priority

Blocker