In "Search Messages" result grid, cannot choose certain columns (like attachment) for display (missing customization options, column picker select)

NEW
Unassigned

Status

--
enhancement
9 years ago
3 years ago

People

(Reporter: bugzilla2007, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [not faceted search])

Attachments

(1 attachment)

Created attachment 406860 [details]
Screenshot: Column pickers compared ("Search Messages" result grid vs. folder display grid)

In the "Search Messages" search result window, user cannot choose to display certain columns (like attachment) in the result grid (to see more properties of the found messages). This unnecessarily limits the functionality of the result grid.

Actual behaviour:
The columns you cannot choose for display in the result grid are:
- Attachments, Read, Received, Account (these can never be shown as they are missing in the column picker)
- Location (we are currently forcing the user to have this column displayed, but we shouldn't. Depending on the search, user might NOT want to see this column, e.g. if you only search within single folders like inbox. Note that we are NOT forcing the user to display this column in a saved search grid, which is the same thing. Tell me if you want this as a separate bug.)

Expected behaviour:
- let user pick whichever column (out of 18, currently) he wants to see in result grid, like we do in folder display

In a normal folder or even saved search display grid, user can select any property of a msg to be displayed as a column in the grid (see attached screenshot which compares the two).
(Reporter)

Comment 1

9 years ago
(In reply to comment #0)
> Actual behaviour:
> The columns you cannot choose for display in the result grid are:
> - Attachments, Read, Received, Account
Sorry, it's just
- Attachments, Received, and Account
(Reporter)

Updated

9 years ago
Duplicate of this bug: 503316

Comment 3

9 years ago
true. always been that way.

xref:  bug 297251, bug 468673
Severity: normal → enhancement
Whiteboard: [not faceted search]
Version: 3.0 → unspecified
Duplicate of this bug: 553602

Comment 5

9 years ago
I care only about attachment. Not sure what Account refers to. I guess I never use it :  )

Thanks


Michelle
Duplicate of this bug: 751125

Comment 7

3 years ago
I would add that not only is the Attachment column not available as an option to display in the Search Results view, but more importantly you cannot select it as a field to search against.

Presumably the "Search Messages" feature is the comprehensive search option in the product, however it does not provide all the same data points that can be searched using the "Quick Search" feature (attachment status in this case).

I suppose that this needs to be a distinct bug (RFE?) as I could not see it mentioned elsewhere.
(Reporter)

Comment 8

3 years ago
(In reply to pitpawten from comment #7)

Thanks for feedback!

> I would add that not only is the Attachment column not available as an
> option to display in the Search Results view, but more importantly you
> cannot select it as a field to search against.

You can, but only for pop accounts, not for imap (existing bug).

> Presumably the "Search Messages" feature is the comprehensive search option
> in the product, however it does not provide all the same data points that
> can be searched using the "Quick Search" feature (attachment status in this
> case).
> 
> I suppose that this needs to be a distinct bug (RFE?) as I could not see it
> mentioned elsewhere.

No, I'm sure we have bugs filed for that already, try this list:

https://bugzilla.mozilla.org/buglist.cgi?quicksearch=%3Athun%2Cmailn%20attachment%20search%2Cfilter&list_id=12717224

Comment 9

3 years ago
(In reply to Thomas D. (currently busy elsewhere; needinfo?me) from comment #8)

> You can, but only for pop accounts, not for imap (existing bug).

Ok, I am using IMAP accounts exclusively. I'll see if I can find this bug since I know TB knows how to filter on attachments in IMAP messages (can do it in quick filters).

Thanks for the quick reply :)
You need to log in before you can comment on or make changes to this bug.