Comment 5 for bug 1308193

This value is being set in qtorganizer5-eds by QOrganizerEDSEngine::parseTodoStartTime(), which gets the value from a
call to a QOrganizerTodoTime.startDateTime().

Looks like the QOrganizerTodo gets set in ubuntu-ui-toolkit/modules/Ubuntu/Components/plugin/adapters/alarmsadapter_organizer.cpp in AlarmsAdapter::organizerEventFromAlarmData(), which sets the start date and due date from the same value, "alarm.date", where alarm is an AlarmData and date a simple property that gets set in UCAlarm::setDate(date)'s call to d->rawData->date = date. So at that point I think we're back to the qml.

Oddly, ubuntu-clock-app/alarm/AddAlarmPage.qml's function to save a new alarm, saveNewAlarm(), creates a new Date object, updates its time fields based on the user's choices, and appears to leave the date fields unchanged...? I'm less sure about the steps in ubuntu-clock-app though -- nik90, could you give this a little triage?