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 710701 - Allow custom columns in message list (e.g. displaying value of a specific mail header)
Allow custom columns in message list (e.g. displaying value of a specific mai...
Status: RESOLVED DUPLICATE of bug 262536
Product: evolution
Classification: Applications
Component: Mailer
3.16.x (obsolete)
Other Linux
: Normal enhancement
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks: 528259 624896
Reported: 2013-10-23 08:26 UTC by Adam Williamson
Modified: 2021-03-22 15:12 UTC
See Also:
GNOME target: ---
GNOME version: ---

Description Adam Williamson 2013-10-23 08:26:47 UTC
So Evolution lets me change what columns are in the message list for any folder, which is great, but I can only pick from a pre-determined set of columns. Thanks to a fedora devel list thread I just discovered that Bugzilla mails have a fantastically useful set of X-Bugzilla headers, and it'd make my life ever so much easier if I could add one or two of these headers as columns for the message lists in my various Bugzilla folders. But I can't.

So, the feature request is to allow the user to define new 'custom' columns for the message list - obviously one source of 'custom' columns would be mail headers, much like the Mail Preferences / Headers tab lets you type in the names of 'extra' headers to be displayed rather than only letting you check off ones that are already in its list. But there are probably other good sources for 'custom' columns from other use cases.

Executive summary, I really REALLY want an X-Bugzilla-Who column in my Bugzilla mail folders. :P
Comment 1 André Klapper 2014-11-18 18:32:33 UTC
Same here, and I throw 80 EUR into the ring (likely not enough at all as that's needs additional code and UI to define specific headers) that I'd pay anybody who implemented this after that implementation got merged into Evolution.

My current ugly workaround is to define a Label in Evolution for specific header *values*, setting up a mail filter rule, and displaying the Labels column in the message list pane instead.
Obviously this does not scale as you have to define *each* header *value* in the filter rule and a corresponding label for it, and as Evolution's mail filter setup UI does not allow nested conditions (only ALL *or* ANY conditions) as covered in bug 220952.
Comment 2 André Klapper 2015-06-08 13:26:15 UTC
(In reply to André Klapper from comment #1)
I increase my offer to 200 EUR for any merged implementation of this request.
Comment 3 André Klapper 2021-03-20 19:27:31 UTC
Superseded by it seems?
Comment 4 Milan Crha 2021-03-22 15:12:53 UTC

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