[Chandler-dev] Fwd: [Bug 12115] Confusing discrepancy between list
views on Hub and Desktop
mimi at osafoundation.org
Thu Jun 12 12:30:27 PDT 2008
I am forwarding this bug to the Dev-List as I think it's an important
usability issue we should address in the web UI for 1.0:
In the interest of performance, we currently only look 1 month into
the future when loading recurring events into the Triage Table in the
Chandler Hub web UI.
This means that the web UI won't display a recurring event under the
1. the recurring event *starts* more than 1 month into the future
2. you have deleted the next occurrence, creating a recurrence gap of
more than 1 month
3. the recurring event recurs at an interval more than 1 month apart
(e.g. annually recurring holidays)
Given that we will be shipping 1.0- Desktop with a shared U.S.
Holidays calendar, out of the box, I think we need to make it so that
at least Scenario #3 works well in the web UI.
From Randy's comment below, it seems the amount of work required to
correctly load "the next occurrence of a recurring event series" for
all 3 scenarios is out of scope for 1.0
However, we can implement a smaller change that would take annually
recurring events and look 1 year into the future to find the next
Randy, even though Chandler doesn't support bi-monthly and bi-annual
recurrence rules. We do support importing them. Would it be possible
to simply expand this exception to include any recurring events that
have a recurrence rule of more than 1 month?
Is this an accurate summary Randy?
Are we still missing any key scenarios?
I have logged a separate bug to track implementing a more general fix
so that all 3 scenarios listed above will work: https://
Begin forwarded message:
> From: bug-comment at osafoundation.org
> Date: June 10, 2008 11:47:08 AM PDT
> To: mimi at osafoundation.org
> Subject: [Bug 12115] Confusing discrepancy between list views on
> Hub and Desktop
> Randy Letness <randy at osafoundation.org> changed:
> What |Removed |Added
> AssignedTo|randy at osafoundation.org |
> travis at osafoundation.org
> --- Comment #9 from Randy Letness <randy at osafoundation.org>
> 2008-06-10 11:47:06 PST ---
> We can definitely look further into the future. I chose 1 month
> because its a
> good compromise between system resources (the further you look, the
> longer the
> query takes) and how far into the future/past people are concerned
> I guess my thinking was, do I really want to know about something
> that is going
> to occur one year from now? If not, then it makes the query
> execute faster. I
> can change the period and see what happens and if things don't slow
> down too
> much we can keep it like that.
> Another option is to re-write the query apis to allow no end date
> to be used
> when searching for instances and provide an api like
> findNextInstance(startDate), which would find the next instance
> after the given
> date. That would probably be the best option, but would require a
> lot more
> Configure bugmail: https://bugzilla.osafoundation.org/userprefs.cgi?
> ------- You are receiving this mail because: -------
> You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the chandler-dev