Editing alarms re-orders them but the list view isn’t updated

Bug #1488439 reported by Olivier Tilloy
18
This bug affects 5 people
Affects Status Importance Assigned to Milestone
Ubuntu Clock App
Fix Released
High
Nekhelesh Ramananthan

Bug Description

Reproduced with the latest clock app version in the store, as well as with version 3.5.347 that I got from popey.
If I have two alarms and I edit the first one in the list so that its time becomes greater than the time of the second alarm, after saving the changes the time displayed in the list of alarms doesn’t reflect the update.

For instance, if alarm 1 in the list is set to 6:45 and alarm 2 is set to 8:00, if I edit alarm 1 to set the time to e.g. 9:45, the labels in the list aren’t updated, and I’m still seeing 6:45 and 8:00. But if I tap the first alarm in the list (the one that displays 6:45), it in fact edits the 8:00 alarm, and conversely if I tap the second alarm in the list (the one that displays 8:00), it edits the 9:45 alarm.

I guess the list view needs to be updated when done editing an alarm.

Related branches

Olivier Tilloy (osomon)
summary: - Editing alarms re-orders them but the list view isn’t updated and the
- time displayed is wrong
+ Editing alarms re-orders them but the list view isn’t updated
Changed in ubuntu-clock-app:
status: New → Confirmed
importance: Undecided → High
Changed in ubuntu-clock-app:
assignee: nobody → Nekhelesh Ramananthan (nik90)
status: Confirmed → In Progress
milestone: none → 3.5
Revision history for this message
Ubuntu Phone Apps Jenkins Bot (ubuntu-phone-apps-jenkins-bot) wrote :

Fix committed into lp:ubuntu-clock-app at revision 359, scheduled for release in ubuntu-clock-app, milestone 3.5

Changed in ubuntu-clock-app:
status: In Progress → Fix Committed
Changed in ubuntu-clock-app:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.