528889 - Threading of bugs broken in Gmail (new threads created for each bug)

Status: VERIFIED FIXED

(bugzilla.mozilla.org :: General, defect)

Description

[Henrik Skupin [:whimboo][⌚️UTC+2]]

Since the yesterdays upgrade of bugzilla the threading in Gmail is broken. A new comment to a bug causes a new thread to appear and is not stacked within the old thread. That's very annoying when you follow the lifetime of a bug in one and only thread.

Comment 1

[Reed Loden [:reed]]

I don't see any change to old headers... I see a few new ones (such as X-Bugzilla-URL), but I wouldn't think that would cause issues.

Seems like Bugzilla should include a proper References: header. That would fix this for good...

Comment 2

[Reed Loden [:reed]]

(In reply to comment #1)
> Seems like Bugzilla should include a proper References: header. That would fix
> this for good...

Oh, it does! build_thread_marker(), etc. Never mind my comment then. No idea why this is broken.

Comment 3

[Reed Loden [:reed]]

Oh, I see the problem. Hmmph...

In-Reply-To: <[e-mail]/>
References: <[e-mail]/>

vs.

In-Reply-To: <[e-mail]/>
References: <[e-mail]/>

Note http vs. https.

Comment 4

[Reed Loden [:reed]]

Ok, I changed urlbase from http://bugzilla.mozilla.org/ to https://bugzilla.mozilla.org/. That should fix it.

Comment 5

[Frédéric Buclin]

(In reply to comment #3)
> Oh, I see the problem. Hmmph...
> Note http vs. https.

That's a pity. The protocol shouldn't be included, for this exact reason. Marc, why including the protocol?

Comment 6

[Marc Schumann [:Wurblzap]]

Theoretically, there could be different Bugzillas on http and https. So at the time, we decided to include the protocol.

Iirc urlbase is being used to determine the value. Maybe it was changed during the upgrade, together with sslbase.

WONTFIX imo.

Comment 7

[Henrik Skupin [:whimboo][⌚️UTC+2]]

Thanks Reed. With the fix it's fine now.