Bug 1318162 - In-Reply-To in notification emails changed format; threading broke
Summary: In-Reply-To in notification emails changed format; threading broke
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Bugzilla
Classification: Community
Component: Bugzilla General
Version: 5.0
Hardware: All
OS: Linux
medium
low vote
Target Milestone: 5.0
Assignee: PnT DevOps Devs
QA Contact: tools-bugs
URL:
Whiteboard:
Depends On: 458026
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-16 08:10 UTC by Rony Gong 🔥
Modified: 2018-12-09 06:29 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 458026
Environment:
Last Closed: 2016-04-11 01:21:38 UTC


Attachments (Terms of Use)

Description Rony Gong 🔥 2016-03-16 08:10:21 UTC
+++ This bug was initially created as a clone of Bug #458026 +++

Not worth fixing unless easy to fix, but the email headers used to contain:

  In-Reply-To: <bug-446214-196610.com>

but now contain

  In-Reply-To: <bug-446214-196610.redhat.com/>

so new email threads have been created.

It'd be nice to go back to the old format again

--- Additional comment from David Lawrence on 2008-08-06 23:04:40 CST ---

Verified this is indeed broken. Taking and will fix in the next update.

--- Additional comment from David Lawrence on 2008-08-06 23:38:37 CST ---

Patch attached for review to fix the domain name that is in reply to header.
In upstream bugzilla they add the http(s) to the domain name for reasons I am not sure. In 2.18 we had bugzilla.redhat.com as the domain name hard coded into the email template.

The patch hacks the BugMail.pm code to remove the https from the domain name and the trailing slash so it better matches 2.18 behaviour.

Please review

Dave

--- Additional comment from Noura El hawary on 2008-08-07 00:22:52 CST ---

looks Good Dave, I saw it works fine on bz-web2.

Noura

--- Additional comment from David Lawrence on 2008-08-07 00:31:39 CST ---

Thanks Noura. Checking into CVS and will be in the next update.

Comment 1 Jeff Fearn 🐞 2016-04-07 23:35:11 UTC
IMO we should close this, keeping Bugzilla 2 behavior alive forever is unjustifiable technical debt.


Note You need to log in before you can comment on or make changes to this bug.