Scheduling error seen in Indian time zone (+05:30)

Description

In the BiAffect study, the "Go/No-Go Reaction Time" schedule (repeat daily at 8am, expiring after one day) was being retrieved for one day in advance, but was not returning a schedule.

On investigation, the getScheduleWindowsBasedOnEvents(...) method was returning a start and end date time that are not in the timezone of the current request, which is then used to truncate scheduled activities in ways that are not in the user's timezone.

Environment

None

Status

Assignee

Alx Dark

Reporter

Alx Dark

Labels

None

Validator

Erin Mounts

Development Area

None

Release Version History

None

Story Points

3

Priority

Critical
Configure