Bug 622175 - When grouping by thread and sorting by date, the thread uses the wrong date.
When grouping by thread and sorting by date, the thread uses the wrong date.
Product: Fedora
Classification: Fedora
Component: evolution (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Matthew Barnes
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2010-08-07 18:35 EDT by Samuel Irlapati
Modified: 2010-08-23 20:19 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-08-23 20:19:31 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Samuel Irlapati 2010-08-07 18:35:33 EDT
Description of problem:

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

How reproducible:

Steps to Reproduce:
1. Start evolution
2. Group by threads
3. Sort according to date
4. Look at the date filed
Actual results: When grouped by thread, the thread retains the date of the first message in the thread and not the last message, when sorting by date.

Expected results: The thread should use the date of the last message in the thread for sorting. 

Additional info:
Comment 1 Milan Crha 2010-08-23 11:19:01 EDT
Thanks for a bug report. This seems to work fine for me. There is a hidden option to influence this behaviour. Open a gconf-editor and check
the default value is 'true' (checked), and means that threads are sorted by the latest date in it. I suppose you have this option unchecked. The long description states:
     This setting specifies whether the threads should be sorted based
     on latest message in each thread, rather than by message's date.
     Evolution requires a restart.

Could you check the value of the option and try to change it, if necessary, please?
Comment 2 Samuel Irlapati 2010-08-23 20:19:31 EDT
Thank you ... that worked!

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