Comment 1 for bug 1087344

That's because it uses the description of the merge proposal, and it's not clear what's the advantage of using two different descriptions for the same merge proposal, when most projects do a pretty poor job on using even one of them.

Can someone provide more detials of what's the use case, and how are *both* fields used at once?