Open Bug 270910 Opened 20 years ago Updated 2 years ago

implement thread-status as a criterion of all searches/filters

Categories

(MailNews Core :: Search, enhancement)

enhancement

Tracking

(Not tracked)

People

(Reporter: tmb-mozilla-bugzill, Unassigned)

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.7.5) Gecko/20041119 Firefox/1.0 (Debian package 1.0-3)
Build Identifier: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.7.5) Gecko/20041119 Firefox/1.0 (Debian package 1.0-3)

While search is customizable when it comes to headers, there are two properties
of messages that are useful but not consistently available in searches: flags
and thread/response status to a message (first-in-thread, last-in-thread,
no-response-received-to).  These message properties are important for mail
maintenance, and some mail clients support using them for sorting, filtering, etc.

Some of these features have been requested in individual feature requests.  I'm
filing this request to suggest making these properties available consistently
throughout Thunderbird.

Reproducible: Always
Steps to Reproduce:
1.
2.
3.
Flag as criterion is bug 201433.

The thread-status idea is new, as far as I can tell.
Assignee: mscott → sspitzer
Component: Mail Window Front End → Search
OS: Linux → All
Product: Thunderbird → MailNews
Hardware: PC → All
Summary: please make flags and thread-status a consistent part of all searches → implement thread-status as a criterion of all searches/filters
Version: unspecified → Trunk
Product: Browser → Seamonkey
Assignee: sspitzer → mail
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
Status: RESOLVED → UNCONFIRMED
Component: MailNews: Search → Mail Window Front End
Product: Mozilla Application Suite → Thunderbird
Resolution: EXPIRED → ---
Reopening this bug was fine, but changing the component was not correct, I think.  There is substantial back-end work required to implement this feature.
Assignee: mail → nobody
Status: UNCONFIRMED → NEW
Component: Mail Window Front End → MailNews: Search
Ever confirmed: true
Product: Thunderbird → Core
QA Contact: search
Product: Core → MailNews Core
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.