After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 528161 - Cannot change color of Task List
Cannot change color of Task List
Status: RESOLVED DUPLICATE of bug 466656
Product: evolution
Classification: Applications
Component: Tasks
2.22.x (obsolete)
Other All
: Normal normal
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2008-04-15 07:24 UTC by Michael Kopp
Modified: 2009-08-26 06:08 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description Michael Kopp 2008-04-15 07:24:18 UTC 
Please describe the problem:
1. Open Properties of a Task List
2. Change the Color

When closing the color dialog the OK Button of the Task List Properties will go inactive

Steps to reproduce:
1. 
2. 
3. 


Actual results:


Expected results:


Does this happen every time?
yes

Other information:
Comment 1 Michael Kopp 2008-04-15 07:25:07 UTC 
This only happens for 'exchange' Task List's. it works fine for local Task List's
Comment 2 Michael Kopp 2008-04-15 09:21:34 UTC 
ok I actually cannot change anything about the task list properties
Comment 3 Akhil Laddha 2008-04-24 12:43:50 UTC 
I can change color and it will remain there but if i disable account and enable again, color will go away. I have tried in Evolution 2.23.1
Comment 4 Michael Kopp 2008-11-26 07:26:59 UTC 
I just tested this with 2.24.1.1. still the same. try to change anything in properties for an exchange task list and the ok button will grey out.

But the important thing that I found it is that this is not for the personal task list but for a public one that I subscribed too via Folder/Subscriptions!

So maybe that is the key difference!
Comment 5 Akhil Laddha 2008-11-26 07:54:38 UTC 
then it's same as bug 466656
Comment 6 Akhil Laddha 2009-08-26 06:08:31 UTC 

*** This bug has been marked as a duplicate of bug 466656 ***