Last modified: 2013-09-05 00:11:10 UTC
Since searching for keywords in titles is terribly useful when looking for a bug hidden among hundred of other ones, I think many would benefit from Bugzilla displaying 2 summary fields: one featuring a very rough description of the problem that the user met, the other, a technical explanation of the problem given by a developer. For example, Bug 53071 - about=null entries on <figure> elements (because of dom-fragment reuse) is where I was supposed to report that some images'syntax was being duplicated and truncated - on an unrelated note, I ended up reporting this on the wrong one, Bug 49729 - Parsoid: DSR on DOM of some reused images is buggy (causing image fragments to be duplicated on save on some pages) - which has an equally scary name :) This would also avoid that devs rename bugs to make it easier for them to explain what is actually going on there - I think I saw James doing that sometimes. I guess I should be asking the Bugzilla team for this, but I am not doing this if you think it's useless/stupid or if there is already an option somewhere that just needs to be added. Thanks.
I don't think that an issue should have several summaries. It's about finding a good compromise and it'll never work for everybody. You can always enhance or edit the summary (I do that from time to time to make conditions of a bug clearer, or do add further words which people might search for instead, e.g. changing "remove" to "remove / delete" etc). But normally my impression is: The lower in the software stack, the less understandable things get for humans. So you still might be able to add a "human" summary by simply adding it in brackets after the "developer" summary.
