Activity log for bug #1401883

Date Who What changed Old value New value Message
2014-12-12 13:23:28 Nekhelesh Ramananthan bug added bug
2014-12-12 13:24:55 Nekhelesh Ramananthan description In Vivid, the clock app cannot edit alarm correctly since the alarm times chosen is not taken into account due to timezone management by the Ubuntu SDK Alarms Backend. In Vivid, the clock app cannot edit alarm correctly since the alarm times chosen is not taken into account due to timezone management by the Ubuntu SDK Alarms Backend. Steps to reproduce: 1. In the latest vivid images, open the clock app 2. Create a new alarm to ring in the next few minutes and save it. 3. Edit the alarm and change the time. 4. save the alarm What happens: The alarm is not updated with the new alarm time chosen in step 3 What should happen The newly changed alarm time should be used.
2014-12-12 13:25:28 Nekhelesh Ramananthan summary [Vivid][Regression] Alarms times is incorrectly saved when editing an alarm [Vivid][Regression] Alarms times are incorrectly saved when editing an alarm
2014-12-12 14:33:36 Zsombor Egri ubuntu-ui-toolkit (Ubuntu): assignee Zsombor Egri (zsombi)
2014-12-12 14:33:39 Zsombor Egri ubuntu-ui-toolkit (Ubuntu): importance Undecided High
2015-02-24 07:22:09 Zoltan Balogh ubuntu-ui-toolkit (Ubuntu): importance High Critical
2015-02-24 15:58:13 Launchpad Janitor ubuntu-ui-toolkit (Ubuntu): status New Confirmed
2015-02-24 15:58:33 Nekhelesh Ramananthan tags qa-promotion touch
2015-02-26 08:27:55 Zsombor Egri ubuntu-ui-toolkit (Ubuntu): status Confirmed In Progress
2015-02-26 15:09:54 Launchpad Janitor branch linked lp:~zsombi/ubuntu-ui-toolkit/alarm-regression-fix
2015-03-06 18:33:47 Launchpad Janitor branch linked lp:ubuntu/vivid-proposed/ubuntu-ui-toolkit
2015-03-06 19:17:22 Launchpad Janitor ubuntu-ui-toolkit (Ubuntu): status In Progress Fix Released