Closed Bug 253268 Opened 20 years ago Closed 11 years ago

add read status to Message Search results window

Categories

(Thunderbird :: Mail Window Front End, enhancement)

Product:
Thunderbird
Component:
Mail Window Front End
Version:
17 Branch
Platform:
x86
Windows 7
Type:
enhancement
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: worcester12345, Unassigned)

Details

(Keywords: polish) 

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040725 Firefox/0.9.1+ (bangbang023)
Build Identifier: version 0.7 (20040617-pigfoot)

Details are in the "Steps to Reproduce".

Reproducible: Always
Steps to Reproduce:
1. Do a search on messages for some text in the body. This returns a list of
results.
2. Open one of the (unread) messages and read it.
3. Close message.
4. Attempt to mark message as unread once again.

Actual Results:  
Would not allow to mark as unread.

Expected Results:  
Should allow to mark as unread.

Has been doing this for several months and as many versions. BIG inconvenience
for me. Tried searching for this bug, but found none.
This one still exists for the "official" version 0.7+ (20040803).

It has "Open" "File" "Delete" and "Open Message Folder" buttons along the
bottom, but no "Mark" buttons. No little green "read/unread" button in the email
either.

Thanks.
Still there: version 0.7+ (20040817)
i can confirm it in thunderbird branch 0.7+ (20040822)

would rather have the context menu upon right-click
Flags: blocking-aviary1.0?
Flags: blocking-aviary1.0PR?
minusing
Flags: blocking-aviary1.0PR?
Flags: blocking-aviary1.0PR-
Flags: blocking-aviary1.0?
Flags: blocking-aviary1.0-
Is this one at all related? They both have to do with usefulness in the mail
front end.

https://bugzilla.mozilla.org/show_bug.cgi?id=101153 Search messages window has
no intrinsic way of closing itself.

Should this be changed from Thunderbird to Mailnews?


Can we set a target milestone for this bug to either Thunderbird0.8 or 0.9? I'd
like to see SOME milestone set, so this gets addressed. 

Thanks.
Can someone please confirm this bug?
Keywords: helpwanted
Summary: cannot mark mail as unread after opening from search window → can't mark mail as unread after viewing it in search window
changed summary and severity to reflect what I think reporter is asking for...
Severity: major → enhancement
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: can't mark mail as unread after viewing it in search window → add message read column to search results window
I think my original description was more accurate, but I'll leave yours to see
if it makes more sense to someone. It IS a bug, though, as it changes one's
message and does not let one change it back to unread afterwards. If one cannot
change it back themselves, maybe the software shouldn't mark it as read to begin
with. This whole interface needs some work, but all I want is the ability to put
messages back to the status they were in before searching for them.
Severity: enhancement → normal
your description was very specific about what you wanted to do, but the actual
problem is much more general - you can't change the read status (to either read
*or* unread) from the search results window...independent of whether you've read
the message in a stand-alone msg window, etc.
Can we get a target milestone here? Thanks. Even as "bug owner", it won't let me
change or add this.
Flags: blocking-aviary1.1?
Flags: blocking-aviary1.1? → blocking-aviary1.1-
(In reply to comment #10)
> your description was very specific about what you wanted to do, but the actual
> problem is much more general - you can't change the read status (to either read
> *or* unread) from the search results window...independent of whether you've read
> the message in a stand-alone msg window, etc.

Correct. I see some work was done on search recently (Bug 278932), so hopefully
some of the other search functions will be looked at soon.
I guess by unblocking, you have no intention of doing this before 1.1 then. A
real bummer.
Also add "junk status" change button.

I was searching for, and found several messages but could not control click them
to mark as junk from search window.

Thanks.
Summary: add message read column to search results window → add message read , junk status to search results window
I hate to be a pain, and know this is not 100% proper, but I'd like to just keep
this on the radar since search bugs were currently being worked on. Sorry and
thanks.
Flags: blocking-aviary2.0?
Any other operating systems seeing this?
Assignee: mscott → nobody
Keywords: mail6
Flags: blocking-firefox2? → blocking-thunderbird2?
Flags: blocking-thunderbird2? → blocking-thunderbird2-
Keywords: polish
Since some of the junk controls are now being worked on, maybe this could be fixed now as well.
Flags: blocking-thunderbird2- → blocking-thunderbird2?
Any search fixes going in before the 2.0 freeze which this could possibly piggyback in on?
minusing. no one's volunteered and we probably won't get to this for 2.
Flags: blocking-thunderbird2? → blocking-thunderbird2-
Any way we can get this little bugaboo fixed or at least put in ability to block Thunderbird 3 or 4?
Please at least add it to the Thunderbird 3 milestone. Thank you.
QA Contact: front-end
Flags: blocking-thunderbird3?
Please don't abuse blocking flags by using them on any bug that you want someone else to fix for you. A blocker is a bug that we absolutely would not ship that release without fixing. The fact that we were willing to ship 1.0, and 1.5, and 2.0 without fixing this should serve as a very, very strong hint that if nobody volunteers to fix it, we will be willing to ship 3.0 without it, too.
Flags: blocking-thunderbird3?
This is such a minor issue, and version 3 is so far off, where else would one put it to block? There are no version 4 blocking flags yet. 
If you don't understand that there are bugs which, though we would like to have them fixed, should not ever be marked as blocking any release, you don't understand blocking flags at all. Please just don't use them at all, on any bugs.
Worcester12345, "unread" status is available from column picker. are you looking to change the status from the results window?

Note: I'm not aware any columns allow changing the value from results list.

narrowing to one issue (one issue per bug please)
Severity: normal → enhancement
Summary: add message read , junk status to search results window → add read status to Message Search results window
You can change the read status from the result window, by clicking the green "unread" column icon.
Keywords: helpwanted
Version: unspecified → 2.0
Can we request this for 3.1?
(In reply to comment #27)
> Can we request this for 3.1?
We'd need a patch in order to be able to request it and make sure it goes in.
(In reply to comment #10)
> your description was very specific about what you wanted to do, but the actual
> problem is much more general - you can't change the read status (to either read
> *or* unread) from the search results window...independent of whether you've read
> the message in a stand-alone msg window, etc.

This is still a problem in this version:
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.10) Gecko/20100518 Shredder/3.0.6pre
Version: 2.0 → 3.0
I am actually seeing the ability to right click and add the "green dot" in the search results window now. While it has no explanation, and is non-intuitive, it is close to being an answer to this bug.
Version: 3.0 → 3.1
Absent any further work on this bug, I think I'll just leave it at WONTFIX, since it is fixable, but nobody wants to add the "Mark as Unread" to a context menu. Thanks anyhow.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WONTFIX
I would certainly not not fix this, so WONTFIX isn't really the right resolution.  Heck, if you have a patch I'll be happy to review it!  (I'm afraid there are some other, higher-priority, things that I'm working on, so I can't write the code myself.)

Thanks,
Blake.
Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---
Version: 3.1 → 17
OS: Windows XP → Windows 7
This bug is almost 9 years old now. I don't really care about it any more, and it seems nobody else does either. I'm going back to "WONTFIX" status.
Status: REOPENED → RESOLVED
Closed: 13 years ago → 11 years ago
Resolution: --- → WONTFIX
Actually this is wfm, per previous comments. (You can click on the "read" indicator in to toggle read state)
Resolution: WONTFIX → WORKSFORME
You need to log in before you can comment on or make changes to this bug.