changing summary doesn't change the bug email subject

[John A Meinel]

I think this stems from the new AJAX style summary update.

I just changed the title for https://bugs.launchpad.net/bugs/382463 in doing so, I got an email stating:
** Summary changed:

- BzrError: Pack 'd5cce80b2cb441dd3d4c233f7ee33c30' already exists in <bzrlib.repofmt.groupcompress_repo.GCRepositoryPackCollection object at 0x85e076c>
+ 'bzr pack' of an already packed --dev6 repo fails with Pack exists

However, the *subject* of that email was still the original Summary.

Even further, I did another update of the bug, and *that* email continued to use the original Summary as the subject.

My guess is there are 2 copies of the Summary, and the new update code only updates 1 of them.

[Eleanor Berger (intellectronica)]

As a user of Gmail, I'm not sure I'd like that to change, since that would mean a new thread will start for every change in the bug title.

[John A Meinel (jameinel)]

Perhaps they intentionally changed the behavior, but that certainly used to be the effect of changing the summary.

I'm pretty sure gmail respects the "References" field in mail headers, which is a way to line up threads even when the subject itself changes. (Consider the Re: New Subject (was old subject) sort of threads anyway.)

Since initial bug reports sometimes have pretty awful summaries, I find it quite useful to change them into something I can actually track without having to actually read the content.

[Eleanor Berger (intellectronica)]

Could this be a regression as a result of the change to the bug notification infrastructure? The fix itself is quite simple.