[Request] Snooze behavior when you miss the alarm

I have the same problem and it took me until this morning to find out what exactly caused the sudden increase in me oversleeping and being late for work, and it's the second time the behaviour was changed without anything in the changelog.

Initially, when I got my Jolla, the alarm would auto-snooze indefinitely, which was great for me and a nice improvement over the "auto-snooze max 3 times" from my N9. Unfortunately, after getting used to this, this was suddenly changed with one of the firmware updates to the N9 behaviour. Not optimal but I could live with it, hoping there would be a configuration option soon. Now, with 1.0.5.x, it suddenly stopped auto-snoozing altogether, with nothing in the changelog. I usually snooze the first one or two times thinking that it'd go for three more times afterwards so it wouldn't be a big deal if I forgot to snooze once but I kept waking up about an hour late... a bit embarrassing. In the meantime, I've had to set multiple alarms which kind of defeats the purpose. Maybe even stranger is that the calendar does auto-snooze at least once...

So, basically: don't change alarm behaviour without clear notices in the changelog or even in the alarm application/backend. Not everyone reads the changelog carefully and this is critical stuff for a lot of us, which most wouldn't expect to change at all. You can't just change it without expecting problems for a group of people. Also, I would like to be able to configure this behaviour.

Never thought that'd be managed in QML files. I found an alternative solution and the reason why my alarms stopped auto-snoozing. A property, maximalTimeoutSnoozeCount, was added in 1.0.4.20 (not 1.0.5.x as I thought) and defaults to 2. On alarms which were set before this update, this property did not exist yet, so the alarm is dismissed immediately (/usr/share/jolla-alarm-ui/jolla-alarm-ui.qml:63). So, if you want to change the default value, open /usr/share/jolla-clock/pages/ClockEditDialog.qml and change

alarmObject.maximalTimeoutSnoozeCount = 2

to whatever you want but remember, 0 really means no auto-snooze at all. Then, edit and save all your alarms so they will use the new value. You cannot use this method and the attah's method at the same time, as the timeoutSnoozeCounter variable will not be increased on Status.Snoozed, only on Status.Closed.