Bug 401721 - Grouping with intelligent date range is not respecting discussion start from newest message
Summary: Grouping with intelligent date range is not respecting discussion start from ...
Status: RESOLVED WORKSFORME
Alias: None
Product: kmail2
Classification: Applications
Component: message list (show other bugs)
Version: 5.7.3
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-12-03 21:32 UTC by Stephan Olbrich
Modified: 2023-02-18 03:47 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Stephan Olbrich 2018-12-03 21:32:52 UTC
SUMMARY
When using intelligend date range for grouping, the discussion start is always first message and never newest message

I only have a the german text, sorry:
STEPS TO REPRODUCE
1. Goto Configure KMail --> Erscheinungsbild --> Standard-Zusammenstellung --> Einrichten
2. Create or copy a new "Zusammenstellung"
3. In the grouping settings, select intelligent date range and as discussion start, select newest message
4. activate the new Zusammenstellung

OBSERVED RESULT
Threads are sorted by date of the first message (not the newest)

EXPECTED RESULT
Threads should be sorted by date of the newest message

SOFTWARE/OS VERSIONS
Windows: 
MacOS: 
Linux/KDE Plasma: Kubuntu 18.04
(available in About System)
KDE Plasma Version: 5.12.7
KDE Frameworks Version: 5.47.0
Qt Version: 5.9.5

ADDITIONAL INFORMATION

When selecting "exact date" instead of "intelligent date" everything works as expected
Comment 1 Justin Zobel 2023-01-19 00:18:54 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 2 Bug Janitor Service 2023-02-03 05:01:47 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Bug Janitor Service 2023-02-18 03:47:44 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!