Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 318623 - >=mail-client/evolution-2.28.3.1: component -tasks don't handle a selected time in the right way when you use the top line entering a new task
Summary: >=mail-client/evolution-2.28.3.1: component -tasks don't handle a selected ti...
Status: RESOLVED UPSTREAM
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] GNOME (show other bugs)
Hardware: AMD64 Linux
: High normal (vote)
Assignee: Gentoo Linux Gnome Desktop Team
URL: https://bugzilla.gnome.org/show_bug.c...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-05 14:18 UTC by Kai Wüstermann
Modified: 2010-07-16 12:40 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kai Wüstermann 2010-05-05 14:18:02 UTC
Enter a new task using the top line. 
Example: 5.5.2010 18:00 | call Mum

This task will be shown in the normal color of your task list and will not change to red when the time is gone.

When you use the NewTask dialog from the menu evolution handles the color in the right way. At the beginning time the color changes to blue. When the end time is gone the color changes to red. When you don't use a beginning time it changes to blue when the day begins.

It also works in the right way if use you the dialog to change the beginning time on an existing task.

The top line task entering should handle the beginning in the same way like the NewTask dialog when entering an end time. May be 0:00 or 0:01 that day.

Reproducible: Always
Comment 1 Pacho Ramos gentoo-dev 2010-05-08 08:14:51 UTC
Can you please explain me step by step how to reproduce this problem? I always get it in blue :-(

Sorry for the inconvenience, by I use evolution only for mail :-|
Comment 2 Kai Wüstermann 2010-05-08 13:25:58 UTC
I used evolution for years and added the column "end date" the the task view. This seams not to be standard. 

You got two possibilities to open a new task. 

1. The gray line at the top of the task ("Klicken sie hier, um eine Aufgabe hinzuzufügen" is written there, which means "Click here for new task")

a) Klick at the line. -> you get two or more fields for input.
b) Click at the arrow at the left field. -> You get a new click box for choosing date and time.
c) Choose "today", give a name to the task ("test0") and press Enter. -> The new task test is shown in the list in blue.
d) Choose the date again and set a time in the future (of today) in the coming click box. -> The task now changes to the normal color of your task list.
e) Wait until the time of the task is gone. -> The task don't change the color to red as it should.

2) New Task from the menu
a) Click file|new|task in the menu. -> You get a new dialog window.
b) Give a name to the task ("test1"), an end date and time. Click save. -> The new task test1 is shown in the list in blue.
c) Wait until the time of test1 is gone -> The task changes the color to red as it should.

Next tests:
3) Click on the arrow of the date in "test0" and give a a new time in the future. -> The color will not change.

4) Click on the arrow of the date in "test0" and change the date to yesterday without deleting the time. -> The color will not change to red like it should.

5) a)Click double on the task -> You get the dialog window.
b) Now change the Date to today without Changing the time -> Now the behavior is normal even you change any date or time in the list of tasks.
Comment 3 Pacho Ramos gentoo-dev 2010-05-08 17:15:07 UTC
Reproduced and reported upstream:
https://bugzilla.gnome.org/show_bug.cgi?id=618125

Thanks a lot for the full explanation :-)
Comment 4 Pacho Ramos gentoo-dev 2010-06-16 11:34:17 UTC
Can you retry with 2.30?
Comment 5 Pacho Ramos gentoo-dev 2010-07-16 12:40:33 UTC
Reproduced even with trunk and affecting to other distributions, but this will need to be handled directly by upstream, feel free to CC yourself to https://bugzilla.gnome.org/show_bug.cgi?id=618125 to keep you informed about this