Bug 1657809

Summary: Email threading is broken for new bugs
Product: [Community] Bugzilla Reporter: Marcelo Ricardo Leitner <mleitner>
Component: Email NotificationsAssignee: PnT DevOps Devs <hss-ied-bugs>
Status: CLOSED DUPLICATE QA Contact: tools-bugs <tools-bugs>
Severity: high Docs Contact:
Priority: high    
Version: 5.0CC: khong, qgong, sdubroca
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-12-10 14:18:59 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Marcelo Ricardo Leitner 2018-12-10 13:35:27 UTC 
Description of problem:
32849 N + dez 10 bugzilla@redhat (1,6K) [Bug 1657658] New: net: 8021q: move vlan offload registrations into vlan
32850 N + dez 10 bugzilla@redhat (0,8K) ┬─>[Bug 1657658] net: 8021q: move vlan offload registrations into vlan_c
32851 N + dez 10 bugzilla@redhat (0,4K) └─>[Bug 1657658] net: 8021q: move vlan offload registrations into vlan_c

This is happening because message 32849 has:
Message-Id: <201812100855.wBA8toRA058134.prod.bz.phx2.redhat.com>

While message 32850 and 51 have:
In-Reply-To: <bug-1657658-317235.redhat.com/>

Version-Release number of selected component (if applicable):
The latest deployment.

How reproducible:
Always on new bugs
Comment 1 Sabrina Dubroca 2018-12-10 13:46:12 UTC 
And new replies to old bugs aren't threaded with the previous ones:

 3554   + 12-07 bugzilla  │ └─>[Bug 1653376] XXX
 3565 N + 12-10 bugzilla  │ ┬─>[Bug 1653376] XXX
 3566 N + 12-10 bugzilla  │ ├─>[Bug 1653376] XXX
 3567 N + 12-10 bugzilla  │ └─>[Bug 1653376] XXX


With 3554:
In-Reply-To: <bug-1653376-381519.com>

356{5,6,7}:
In-Reply-To: <bug-1653376-381519.redhat.com/>
Comment 2 Tomas Hoger 2018-12-10 14:18:59 UTC 

*** This bug has been marked as a duplicate of bug 1657677 ***