Dashboard Recurrence Notes

Proposal A vs Proposal B

• Bobby: Had a hard time distinguishing the difference between proposal A & B
• Priscilla: B assumes that we don't have stamping. You can view the stamps but not edit
• Bobby comments on structure on how proposal A and B are written

Issue

• Cosmo - is it appropriate to show all the DONE instances for ever. Is it reasonable for Cosmo to pull all this info in.
• If you display one, you would display the upcoming instance only
• How do we handle modifications?
• Showing one line item

• Eliminating stamping does not make this easier

• The upcoming instance displays only.
• The upcoming instance time determines when it appears in NOW and the changeover to next appear.
• Alarms change the time in which the upcoming occurrence appears in the NOW section but not when we change over to the next occurrence.
• Alarm can be set for after the event is done. Need to work out these edge cases.
• Because on the desktop we have complicated tickling scenarios (alarms before/after) we don't really know exactly what will happen.
• When do you decide to disappear it to show the next occurrence.
• If you have one in NOW with an alarm that fires afterwards

• Being able to display more than one line item - talk to Jeffrey
• Seems like there is some way we can handle the one line item
• Talk to Jeffrey about

• Quick item entry box for notes only - text is the title
• Is the entry box at the top of the calendar - not sure
• It's less useful for the calendar

• Communications stamp - formatting the email shouldn't be an issue
• If the user has entered email addresses in these fields then clicks the Mail To: we then add anything valid into the To field.

• Change recurrence to be a table
• Jeffrey might have a table or we can draft one

• Spec - section numbers
• Table listing out all the recurrence rules and requirements.

• Meeting with Jeffrey - coordinate for when he gets back
• Priscilla will work on the recurrence

-- SheilaMooney - 17 Apr 2007