Closed Bug 408971 Opened 17 years ago Closed 17 years ago

eMail to event/task conversion: wrong start time

Categories

(Calendar :: Lightning Only, defect)

defect
Not set
minor

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: andreas.treumann, Unassigned)

Details

STEPS TO REPRODUCE:
===================

- convert a eMail in a task or event   

RESULT:
=======

- the start time is wrong (current time)

EXPECTED RESULT:
================

- the start time should be the next full hour

REPRODUCIBLE:
=============

- always
Flags: blocking-calendar0.8?
Flags: blocking-calendar0.8? → blocking-calendar0.8+
> - the start time should be the next full hour
start time for new events is current hour so this should be also changed for consistency (not sure if there is already bug for this)

Version: Trunk → unspecified
I don't quite understand this bug. You say the start time should be the next full hour. Why? I would probably expect the start time being the date of the email.

Przemyslaw is right, the behavior of the start date is not quite consistent:

Create...
* an event via new event button or unifinder: Current hour, 0 minutes
* a task via new task button: Current hour and minute
* an event or task via dragndrop from an email: Current hour and minute.
* an event via views: Time in view (correct)


Is this really a blocker for 0.8 ?
I agree with Philipp, that this is not an 0.8 blocker. Moving back to nomination so that Daniel can reconsider.
Flags: blocking-calendar0.8+ → blocking-calendar0.8?
->Philipp Kewisch: Take a look at http://wiki.mozilla.org/Calendar:SMB_Event_Dialog#Menu:_File -> New/Event: Start time has to be on the next full hour. E.g. it is 9:40am the preselected time has to be 10:00am. (specification author is Christian Jansen)
moved back to wanted list
Flags: blocking-calendar0.8? → wanted-calendar0.8+
Bug 413516 contains changes to make every above noted item creation method use the "next full hour" method. Therefore this bug can be closed.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.