본 사이트는 여러분의 사용자 경험을 개선하기 위해 유지 보수를 진행하는 동안 기능이 제한됩니다. 도움말로 문제가 해결되지 않고 질문을 하고 싶다면 Twitter의 @FirefoxSupport 및 Reddit의 /r/firefox 채널을 활용하세요.

Mozilla 도움말 검색

고객 지원 사기를 피하세요. 저희는 여러분께 절대로 전화를 걸거나 문자를 보내거나 개인 정보를 공유하도록 요청하지 않습니다. "악용 사례 신고"옵션을 사용하여 의심스러운 활동을 신고해 주세요.

자세히 살펴보기

Keep messages grouped by thread, when the parent has been archived?

  • 2 답장
  • 1 이 문제를 만남
  • 6 보기
  • 최종 답변자: kb

more options

I am receiving a large number of automated messages that would profit greatly from threading, but they are not threaded, after I archive the parent message, see screenshot.

Is there some way to keep these threads together, after the original message has been archived?

The JIRA of the same thread all have the "In-Reply-To" header and "References" header set to the root message.

Keeping the root messages in my inbox is not viable; There would simply be too many.

I am receiving a large number of automated messages that would profit greatly from threading, but they are not threaded, after I archive the parent message, see screenshot. Is there some way to keep these threads together, after the original message has been archived? The JIRA of the same thread all have the "In-Reply-To" header and "References" header set to the root message. Keeping the root messages in my inbox is not viable; There would simply be too many.
첨부된 스크린샷

모든 댓글 (2)

more options

without the parent the threading is broken as they are all peers, although replies to those would thread.

Right clicking and selecting view in conversation will display the threaded conversation.

There are some hidden preferences for Threading, but I do not know if they will get you what you want. This article basically tells you how to not do what you want, but documents the settings. http://kb.mozillazine.org/Mail.thread_without_re

more options

Matt said

http://kb.mozillazine.org/Mail.thread_without_re

Already tried those; They don't change the behavior.

The issue is mainly that such notification emails heavily clutter the Inbox, so being able to view them as a thread (Ctrl+Shift+O) is a useful feature, but the larger issue is keeping the Inbox organized.

The end result is that active discussions are compacted into a single thread, and hard to find between all the notifications, significantly impacting workflows.