Open Bug 218208 Opened 21 years ago Updated 2 years ago

[mailviews] Watch/ignore status of thread should be available as custom view condition

Categories

(MailNews Core :: Backend, defect)

defect

Tracking

(Not tracked)

People

(Reporter: smjg, Unassigned)

References

(Blocks 5 open bugs)

Details

(Keywords: ux-control)

We could do with a "Thread Status" option being added to the conditions available for customising mailviews. [ Thread Status v] [ is v] [ watched v] +-------+ +----------+ | is | | watched | | isn't | | ignored | +-------+ | neither | +----------+
Oops ... yet another mistyped bug number. This blocks bug 207862, not bug 207864!
Blocks: 207862
No longer blocks: 207864
Blocks: 214286
Blocks: newsviews
No longer blocks: mailviews
Blocks: 236849
Product: Browser → Seamonkey
Assignee: sspitzer → mail
So this is actually more a request for having a message filter "thread is [not] watched", because that's how views work. This for itself if not actually "hard", just tedious. ;-)
Small correction: The filter would be is watched Thread marked as is not ignored Or probably as two filters.
Doh. Oops. Sorry for bugspamming. :((
(In reply to comment #2) > So this is actually more a request for having a message filter "thread is > [not] watched", because that's how views work. More than what? (In reply to comment #3) > Small correction: The filter would be > > is watched > Thread marked as > is not ignored > > Or probably as two filters. So you think we should leave out the possibility of doing 'neither watched nor ignored' in one condition? Any particular reason?
> > So this is actually more a request for having a message filter "thread is > > [not] watched", because that's how views work. > > More than what? More than just for views - the filter will be available for regular filtering also. > So you think we should leave out the possibility of doing 'neither watched nor > ignored' in one condition? Well, it'd be somewhat superfluous (since you could use "not watched and not killed", but so is "to or CC", so I'd say that'd be fine. I just forgot about comment #0 when posting comment #3. :-(( I'll try to find some "spare cycles" to work on this, but anyone who wants to give it a shot can just step in and implement it! ;-)
(In reply to comment #6) >> So you think we should leave out the possibility of doing 'neither >> watched nor ignored' in one condition? > > Well, it'd be somewhat superfluous (since you could use "not > watched and not killed", but so is "to or CC", so I'd say that'd be > fine. Actually, it isn't quite superfluous - it would open up more possibilities for combining the status of 'neither watched nor ignored' with other conditions.
Product: Core → MailNews Core
Assignee: mail → nobody
Component: MailNews: Main Mail Window → MailNews: Backend
Product: Mozilla Application Suite → Core
QA Contact: esther → backend
See Also: → 504020

I consider this missing view to be a bug. In some cases it is near impossible to find a message that has been marked ignored. In my case it took 20-30 minutes to find the message.

  1. dark theme enabled
  2. accidentally marked a message as ignored
  3. I moved on in my work - selected a different message, and also scrolled away from the location of the marked message
  4. I later discovered at the bottom of the screen the alert "Replies to the thread "<subject>" will not be shown"
  5. I didn't notice the alert because it's at the bottom of the screen (the result of ignoring a thread would be better shown near the affected message) and it also wasn't obvious because of a theme issue - I had dark theme enabled, and the alert is thus dark gray against a black background
  6. it shows only a partial subject, so it doesn't uniquely identify the thread's subject
  7. the text of the alert can't be copied
  8. clicking it doesn't take you to the message
  9. I tried to find the message using quick filter against the partial subject, but it doesn't show ignored messages
  10. View Threads can't be set to ONLY display ignored messages (this bug report)

In short, it can be near imposible to find the affected message. This bug report needs to be implemented.
#8 might be a suitable alternative.

Type: enhancement → defect
Keywords: polishux-control

I'm seeing icons in the Thread pane for Watched and Ignored Threads with matching check marks in the Message menu item, and an Ignored Threads menu item under View > Threads I can use to find Ignored Threads after they get hidden in the 91.5.1 release candidate on Windows 10.

If I go to the Message > Ignore Thread menu item after ignoring a thread and click it again, it unignores the thread. Also, can right-click on the thread if visible using View > Threads > Ignored Threads and remove the check mark there.

Note that this bug report isn't about View -> Threads, but about the options available for customising mailviews (View -> Messages -> Custom Views in Thunderbird; I'm not sure whether it's the same in current SeaMonkey).

Right you are. I wondered what "mailviews" referred to. I never use the toolbar widget - it's removed.
I'll file a new bug for my comment 8

Summary: [mailviews] Watch/ignore status of thread should be available as view condition → [mailviews] Watch/ignore status of thread should be available as toolbar view condition

Oh, you mean adding the Mail Views toolbar item from Customize.

You can't add it to the toolbar, select View > Customize > New, which has another Customize item in the first drop-down which starts with "Subject".

I don't use the toolbar item, or would know how to add the ignored status.

The term "toolbar view" is confusing as the toolbar control is just one UI for using the feature, which appears to be relatively new. Some users might not be using this UI but just View -> Messages -> Custom Views. Changing it to "custom view" as this seems to match best with the official name of the feature (which has been known as "mailviews" in the community).

Summary: [mailviews] Watch/ignore status of thread should be available as toolbar view condition → [mailviews] Watch/ignore status of thread should be available as custom view condition
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.