Bug 389511 - JIRA emails are not threaded in message list
Summary: JIRA emails are not threaded in message list
Status: RESOLVED WORKSFORME
Alias: None
Product: kmail2
Classification: Applications
Component: message list (show other bugs)
Version: 5.6.3
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-01-27 14:03 UTC by Charlemagne Lasse
Modified: 2022-12-15 05:15 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Charlemagne Lasse 2018-01-27 14:03:39 UTC
See also https://bugs.kde.org/show_bug.cgi?id=319909

JIRA emails I receive are not threaded in message list. I tried all three methods: Perfect, Perfect and Reference, Perfect, Reference and Subject.

I think the reason is that these messages have both In-Reply-To and References headers filled, but there is never a parent with such ID. So they are in the same thread, but there is never a thread parent. JIRA developers say that it is set so, because you can start receiving mail during issue workflow, not from the begining, so they mark threads correctly with the same ID, but there is never parent.

I suspect that for some reason it never gets to Thread by Subject pass, so it would be matched perfectly. Subject is complicated as well.

Below are two samples of messages in same thread, but not threaded in KMail2.

Delivery-date: Thu, 16 May 2013 14:34:33 +0200
Date: Thu, 16 May 2013 14:33:37 +0200 (CEST)
From: "X" <jira@company.com>
To: X@company.com
Message-ID: <JIRA.139572.1368538114000.23735.1368707617359@jira.company.com>
In-Reply-To: <JIRA.139572.1368538114000@jira.company.com>
References: <JIRA.139572.1368538114000@jira.company.com>
MIME-Version: 1.0
Precedence: bulk
Auto-Submitted: auto-generated
X-JIRA-FingerPrint: fb2cdf5241d4431752db9b302372a195
Received-SPF: none client-ip=172.31.254.38; envelope-from=jira@company.com;
 helo=company.com
Subject: [Mailing.list] [company JIRA] (XXX-897) Error changing Permision
	profile for agents
X-BeenThere: mailing.list@company.com
X-Mailman-Version: 2.1.15
List-Id: <mailing.list.company.com>


Delivery-date: Thu, 16 May 2013 14:40:27 +0200
Date: Thu, 16 May 2013 14:39:37 +0200 (CEST)
From: "X" <jira@company.com>
To: mailing.list@company.com
Message-ID: <JIRA.139572.1368538114000.23744.1368707977266@jira.company.com>
In-Reply-To: <JIRA.139572.1368538114000@jira.company.com>
References: <JIRA.139572.1368538114000@jira.company.com>
MIME-Version: 1.0
Precedence: bulk
Auto-Submitted: auto-generated
X-JIRA-FingerPrint: fb2cdf5241d4431752db9b302372a195
Received-SPF: none client-ip=172.31.254.38; envelope-from=jira@company.com;
 helo=company.com
Subject: [Mailing.list] [company JIRA] (BUGS-897) Error changing Permision
	profile for agents
X-BeenThere: mailing.list@company.com
X-Mailman-Version: 2.1.15
List-Id: <mailing.list.company.com>


Reproducible: Always

Actual Results:  
Message list not threaded.

Expected Results:  
Message list threaded by References.
Comment 1 Justin Zobel 2022-11-15 22:58:26 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 2 Bug Janitor Service 2022-11-30 05:14:56 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Bug Janitor Service 2022-12-15 05:15:02 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!