Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#16 I ask for a statement

v0.0.6
closed-wont-fix
Kontact Bug (6)
5
2011-05-13
2011-04-15
ialexa
No

Step one:
Evolution: create a new task > fill the fields "Start date", "Start time" and "Due date" > DON'T fill the field "Due time" (the field must remain empty)> OK > Synchronize

Actual: Open the To-do in Contacts: the checkbox "Time associated" and the "start time" are not activated.

Target: I don't know what the behavior should be here. I guess that the checkbox must be activated and the due time must be visible.

2. Step two:
Evolution: create a new task > fill the fields "Start date", "Due date" and "Due time (9:00 o'clock)" > DON'T fill the field "Start time" (the field must remain empty) > OK > Synchronize

Actual: Open the To-do in Contacts: the checkbox "Time associated" is activated. The start time is 02:00 o'clock and the due time is 11:00 o'clock.

Target: The case is similar, but the behavior is completely different. I guess the start time must not be visible and the end time must be 9:00 o'clock.

Can anybody please explain the wright behavior of / in this case! I think that the problem is in Contacts. It always requires "start time" and "end time" if the checkbox "Time associated" is active.

Discussion

    • assigned_to: nobody --> hhelwich
     
  • The kolab spec is not clear at this point. The only comment i find is [1]:

    "The start-date is optional for tasks. For events, it is required. If they are there, they can either have a date or a datetime as the type. Parsing this is just a matter of looking at the length of the date string. In the case of an all day event (floating event) the end-date MUST be in date only format"

    Kolab format spec does not take account of a mixed date/datetime configuration.

    Right now the Converter Lib allows mixed date/datetime fomats for start and due date like evolution does. Kontact does not support this.
    Kontact seems to take the format of the due date to decide if it is a full day task or a task with time. So if the due time is set it also displays a time for the start date even if this is date format without time. It displays 2:00 in my case so that is equal to the current local time zone offset here. Kontact seems to take the 0:00 UTC time to indicate the start time of the date.

    I think this is something like a bug in Kontact that results from the vague kolab specification. In my opinion this is ok to stay with the current conversion.

    [1] http://kolab.org/doc/kolabformat-2.0-html/x242.html

     
    • labels: --> Kontact Bug
    • status: open --> open-wont-fix
     
  • ialexa
    ialexa
    2011-05-13

    • status: open-wont-fix --> closed-wont-fix
     
  • ialexa
    ialexa
    2011-05-13

    Ok, when I fill the Start- und Duetime at the same time I've had no Problems. I guess the bug can be closed.