Closed Bug 291171 Opened 20 years ago Closed 20 years ago

Search messages (and thusly search folders) should be able to search on the flag

Categories

(Thunderbird :: General, enhancement)

x86
Windows XP
enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: jack, Assigned: mscott)

References

()

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.7) Gecko/20050414 Firefox/1.0.3
Build Identifier: Thunderbird 1.0.2 winxp

I think it would be nice if I could create a search folder based only on a flag;
 Currently, I can almost get this by sorting on the Flag column, but then I have
to scroll around to find out whether they are at the top or the bottom of the
list, and I can't sort again on any other columns.

Reproducible: Always

Steps to Reproduce:
1. Right click a folder
2. Click "Search messages"
3. Click the dropdown menu for field to search
4. see That "flag" isn't in it.

Actual Results:  
The dropdown list has only Subject, Body, and a bunch of message header fields,
and the option to search any other message headers;  Upon inspection, I have
been unable to find a header that indicates whether a message is flagged.

Upon inspection, I have inferred that "X-Status: F" means that a message has a
flag, but for some reason, searching on the custom header "X-Status" "is" or
"contains" "F" doesn't do it. 

Expected Results:  
I would like to be able to see "Flagged?" in the list of fields to search on. 
The  next two fields may need to be condensed into one, since it's a boolean value.
in trunk builds (but perhaps not 1.0 builds), you can search on msg status is
flagged.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → WORKSFORME
Is this enhancement (supposedly in trunk builds) going to make it back into the
mainline at any point?  This is my single remaining issue with Thunderbird
functionality.
the trunk *is* the mainline. The next release off the mainline will be 1.5,
which is currently in its second beta.
You need to log in before you can comment on or make changes to this bug.