[Feature] Skip next occurence of a repeating alarm

Bug #1438037 reported by Riccardo Padovani
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Ubuntu Clock App
In Progress
Eran Uzan
Ubuntu UX

Bug Description

I've two alarms on my phone: one for all week days (but Sunday) and one for Sunday.

Some evening I choose to don't wake up the next morning, so I go to clock app and deactivate the weekly alarm: the problem is, the next evening I've to remember to reactivate it.

A very useful feature would be to have a button (a swipe? A long press?) to skip next occurence of the alarm: when I click on it removes next occurence of the alarm, but doesn't deactivate the alarm, so I don't have to remember to reactivate it.

Revision history for this message
Nekhelesh Ramananthan (nik90) wrote :

hmm this feature request seems very specific to me and as such requires a lot of effort due to,
1. Using a unusual input to activate such a feature although I guess we can brainstorm further to fix this. At the moment we already use the long press to allow for multi-selection feature which is standard through the platform. The swipe is used for delete at the moment.
2. The alarms backend that we use qtorganizer5-eds would also not support such a functionality since removing one day of the recurrence for instance wednesday would result in all the wednesdays being removed.

Either way I will keep this bug open, there are still lot of high priority alarms to be fixed first. So I wouldn't expect a quick fix for this.

Changed in ubuntu-clock-app:
milestone: none → 3.x.backlog
importance: Undecided → Wishlist
Revision history for this message
Eran Uzan (etherpulse) wrote :

If found an hack that seems to work as long as all you want it to skip an alarm within the next 24 hours...

does this answer this issue or do you prefer to change the backend to support this logic?

Revision history for this message
Michal Predotka (mpredotka) wrote :

Thanks for taking your time to create fix for this bug. Sorry nobody from the Clock team responded yet but, to be honest, for various reasons nobody is actively working on the Clock app at the moment. That said I believe we need an input from Ubuntu-UX team about implementation of this functionality.
Personally I'd like to have this bug fixed together with bug #1518892 (Switching alarm on/off) and have both 'edit' and 'skip next alarm occurrence' as trailing actions.

Revision history for this message
Eran Uzan (etherpulse) wrote :

Hey Michal,

I've added the edit trailing action for each alaram instead of onclick to the current Merge Proposal.
If anychage is need to the pause function i`ll gladly change it.

Thanks for all the hard work :)

Revision history for this message
Eran Uzan (etherpulse) wrote :


I've detached the trailing edit action change from the pause alarm changes and created a new MP.

Changed in ubuntu-clock-app:
milestone: 3.x.backlog → 3.8
status: New → In Progress
assignee: nobody → Eran Uzan (etherpulse)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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