Events scope: Alarm today not in cat id "Events today"

Bug #1503347 reported by Kyle Nitzsche
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
The Savilerow project
New
Undecided
Unassigned

Bug Description

The events scope currently (version 1.1.1) provides results whose date is today in a category whose ID is "Events today".

Expectations:

* This category id must *always* be returned so that the Today scope always has a result and the events child scope always displays there.
* If there are no events or alarms (set from the clock app), the category should have a single result saying "No events today" THIS SEEMS TO WORK
* if there are any alarms set for today, this category should have a result for each alarm THIS DOES NOT WORK.

So the bug is that when there are no events today and there is one (or more) alarms, the Events scope must return return a category with id "Events today" with an event for each alarm.

What happens now when there are no events today and there is at least one alarm?
* a Different category id is returned: "Upcoming events". AND, this does not contain results for any alarms! So, the Today scope shows NOTHING for Events scope.

Please note: we should probably modify the tasks scope to return results by *keyword* and aggregate them in Today scope by keyword instead of using this category stuff.

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.