Bug 212328 - [RHEL5] Evolution doesn't apply changed 'hide completed tasks' setting immediately.
Summary: [RHEL5] Evolution doesn't apply changed 'hide completed tasks' setting immedi...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: evolution
Version: 5.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Matthew Barnes
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-10-26 10:44 UTC by Petr Muller
Modified: 2016-09-20 02:04 UTC (History)
1 user (show)

Fixed In Version: evolution-2.12.3-8.el5
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-03-20 14:09:05 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Petr Muller 2006-10-26 10:44:55 UTC
Description of problem:
Evolution doesn't apply changed time in 'hide completed tasks' setting 
immediately.  If you change the time after task should be hidden, and complete 
some task, it is hidden after old value of time, not the new.
If you reload the task list somehow (e.g. restart Evolution, switch to mail and 
back to tasks, etc), the new settings applies.

Version-Release number of selected component (if applicable):
Evolution 2.8.0

How reproducible:
always

Steps to Reproduce:
1. Create a few tasks and make sure 'Hide completed tasks' is disabled in 
preferences
2. Change settings to be 'Hide completed tasks after 1 minute'
3. Make one task completed
4. Wait one minute. Completed task hides.
5. Change settings to be 'Hide completed tasks after 0 minute'
6. Make other task completed. It hides after 1 minute, but it should hide 
immediately.
  
Actual results:
Changed settings are applied after reloading the task list somehow.

Expected results:
Changed settings are applied by closing settings dialog.

Additional info:

Comment 1 Matthew Barnes 2008-03-16 22:39:07 UTC
RHEL 5.2 will re-base Evolution from version 2.8.0 to version 2.12.3.
Can you please test whether this bug is still present in RHEL 5.2?

Comment 2 Petr Muller 2008-03-20 12:27:32 UTC
This bug seems to be fixed in RHEL5.2 evo

Comment 3 Matthew Barnes 2008-03-20 14:09:05 UTC
Thanks for responding.  I'll close this as CURRENTRELEASE then.


Note You need to log in before you can comment on or make changes to this bug.