Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
When auto-moving within message list, move to "most preferred" or "least preferred unread". Auto moving within messages happens pretty often when e.g. user switches to the folder from another folder or when she clears search filter.
Version-Release number of selected component (if applicable):
evolution-2.28.3-24.el6.x86_64
How reproducible:
often
Steps to Reproduce:
1. move to the folder from another folder OR apply a search filter and clear it again
2.
3.
Actual results:
evolution moves in folders lists to one of following:
* the top of message list (in my case, to the oldest - least
interesting - actually)
* somewhere randomly among unread messages
Expected results:
evolution moves in message list so that "least preferred" unread message is visible - in my case of sorting by date, it's the oldest unread message
if the above is not possible, then it should move to "most preferred" message - in my case, the newest one aka the bottom of the list.
Additional info:
I looked briefly in the code and the rule for selecting a message when moving to a folder looks close to this:
a) if previously selected message exists, select it
b) if it doesn't exist or is not saved (like when multiple messages were
selected when leaving the folder), then pick message with the same uid from
the previous folder (usually doesn't apply)
c) then pick first message in the list
That's only a rough view from the code, though.
Current evolution, the 3.4.0, uses different approach, it picks unread message, if it cannot restore previously selected message. It's part of 2.30 too, according to:
https://bugzilla.gnome.org/show_bug.cgi?id=621839
Thus patches available.
Comment 2RHEL Program Management
2012-07-10 06:35:32 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Comment 3RHEL Program Management
2012-07-10 23:09:05 UTC
This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development. This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.
I noticed one thing: it often sort-of-works - when switching to a folder with multiple unread, evo centers at the oldest unread message, but it leads to wrong behaviour in threaded view with Date (ascendin) sort:
[lots of old threads]
- thread a) start
--
--
--- unread message #2 <-- topmost unread
[other threads]
- thread b) start
--
--- unread message #1 <-- oldest unread
--
--- unread message #3 <-- newest unread
as you can see, topmost unread should be focused when user switches to the folder instead of oldest unread because sorting of threads based on thread newes message can differ wildly from message order in flat view.
Comment 5RHEL Program Management
2012-12-14 07:08:07 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHSA-2013-1540.html
Description of problem: When auto-moving within message list, move to "most preferred" or "least preferred unread". Auto moving within messages happens pretty often when e.g. user switches to the folder from another folder or when she clears search filter. Version-Release number of selected component (if applicable): evolution-2.28.3-24.el6.x86_64 How reproducible: often Steps to Reproduce: 1. move to the folder from another folder OR apply a search filter and clear it again 2. 3. Actual results: evolution moves in folders lists to one of following: * the top of message list (in my case, to the oldest - least interesting - actually) * somewhere randomly among unread messages Expected results: evolution moves in message list so that "least preferred" unread message is visible - in my case of sorting by date, it's the oldest unread message if the above is not possible, then it should move to "most preferred" message - in my case, the newest one aka the bottom of the list. Additional info: