On Fri, 13 Sep 2013 17:35:20 +0200 Jakub Filak <jfilak(a)redhat.com&gt; wrote: > Hello, > > a bugzilla ticket [1] requiring a better Bugzilla summary field text > produced by abrt has been filed. Before I start changing the bug > summary format I'd like to do a little survey: > > What would you like see in the bug summaries produced by abrt? I actually disagree with the reporter of the bug. I prefer to have the component name in the subject of the bug. It's true that you can look this up by going to the bug on the web and that it's in the initial email, but after that the context of update emails is not there, so it's harder for me to know _which_ of the many abrt bugs this is.

On Mon, Sep 16, 2013 at 10:36:41AM +0200, Karel Zak wrote: > On Fri, Sep 13, 2013 at 10:38:41AM -0600, Kevin Fenzi wrote: > > On Fri, 13 Sep 2013 17:35:20 +0200 > > Jakub Filak <jfilak(a)redhat.com&gt; wrote: > > > a bugzilla ticket [1] requiring a better Bugzilla summary field text > > > produced by abrt has been filed. Before I start changing the bug > > > summary format I'd like to do a little survey: > > > > > > What would you like see in the bug summaries produced by abrt? > > > > I actually disagree with the reporter of the bug. > > > > I prefer to have the component name in the subject of the bug. It's > > true that you can look this up by going to the bug on the web and that > > it's in the initial email, but after that the context of update emails > > is not there, so it's harder for me to know _which_ of the many abrt > > bugs this is. > > Please, fix/improve your email client UI. All bugzilla emails > contain all necessary information in email header: Because opening email headers is indeed so convenient. > for example: > > X-Bugzilla-Reporter: > X-Bugzilla-URL: https://bugzilla.redhat.com/ > > > For example if you use mutt then all you need is to add > > unignore X-Bugzilla-Product X-Bugzilla-Component This is nice and handy, but I actually don't know many client offering this opeiton. /me gonna add this option to his muttrc (lucky that I do use mutt here and there).

For example if you use mutt then all you need is to add unignore X-Bugzilla-Product X-Bugzilla-Component to your .muttrc. It's pretty common that we don't have component name in BZ summary...

On Mon, Sep 16, 2013 at 12:34:50PM +0200, Till Maas wrote: > On Mon, Sep 16, 2013 at 10:36:41AM +0200, Karel Zak wrote: > > > For example if you use mutt then all you need is to add > > > > unignore X-Bugzilla-Product X-Bugzilla-Component > > > > to your .muttrc. > > > > It's pretty common that we don't have component name in BZ summary... > > But this does not show the component in the "index" view, or can this be > changed as well? I always add the component to the summary for Bugs I > report to get this information before I need to open the mail itself. "Change Columns" link in the search output.

Please, fix/improve your email client UI. All bugzilla emails contain all necessary information in email header:

For example if you use mutt then all you need is to add unignore X-Bugzilla-Product X-Bugzilla-Component to your .muttrc.

It's pretty common that we don't have component name in BZ summary...

> I wonder if someday it would make sense to customize this per user? > Possibly too much complexity... > > kevin ABRT provides per component customization. https://github.com/abrt/abrt/wiki/FAQ#component-specific-bugzilla-bug-for...

> ABRT provides per component customization. > > https://github.com/abrt/abrt/wiki/FAQ#component-specific-bugzilla-bug-for... Excellent. Given that almost no packages are shipping these, is there any guideline or guidance how to do so? Just add them to our packages? Anything we need to require?

Might be nice to work with FPC/packaging list and come up with a clear guideline for these. kevin