I'm guessing this is the "I wants alarms to be pinned to a specific moment in time and not the time the alarm is set to in the current timezone" thing.
It would be nice if this was an option but I can't really fault them for not including it since it's kinda niche.
As I wrote, I can no longer trust the alarm. I’m talking about a supported use case which broke, not a niche and unsupported situation.
This seems to be have been fixed in 16.4, but before that I would:
1. Pull down to show Spotlight search.
2. Type “alarm” and tap “Create Alarm”.
3. Set a time and tap “Done”.
The feedback message would tell me the alarm was set to a different time, with multiple hours of difference.
This is using only first-party features to do a basic task and even that didn’t work right. I could reproduce it reliably. Luckily the message was correctly showing the wrong time that was set and I double-checked it to notice.
All the other issues I mentioned still have open feedbacks about it. All but one are regressions, the other is a security flaw which has always been there.
It would be nice if this was an option but I can't really fault them for not including it since it's kinda niche.