Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

bugzilla whine/email.txt.tmpl

17 views
Skip to first unread message

Rogier Bosman

unread,
Nov 24, 2009, 8:07:42 AM11/24/09
to
I want to add the component of the bug in the mail report configured
with whining. I found out that the template I need to alter is whine/
email.txt.tmpl. But when I try to add the following line
Component: [% bug.component %]
in the template, it leaves the part after the : blank.

Can someone please help me in putting the component in the report
mail?


Thanks,
Rogier

lippoliv

unread,
Nov 25, 2009, 7:57:20 AM11/25/09
to

I dont know how to get this mail, so I can't try it out but: all
parameters are shown with for example [%+ bug.priority %], so try
change [% bug.component %] to [%+ bug.component %]...

I would be more helpful but as I said: I can't get theese mail sry :-)

lippoliv

unread,
Nov 25, 2009, 8:35:17 AM11/25/09
to

May tage a look in whine.pl there is an function "sub run_queries {"
and there is
my @searchfields = (
'bugs.bug_id',
'bugs.bug_severity',
'bugs.priority',
'bugs.rep_platform',
'bugs.assigned_to',
'bugs.bug_status',
'bugs.resolution',
'bugs.short_desc',
'map_assigned_to.login_name',
);

may you have to add 'bugs.component', then you can use it !?

Kent Rogers

unread,
Nov 25, 2009, 8:45:54 AM11/25/09
to support-...@lists.mozilla.org
If you want to add a field to the whine email, I believe you need to add
it to the list of fields that are queried in whine.pl and then passed to
the template via $queries->{'bugs'}. Basically, add it to the
@searchfields list.

- Kent

Rogier Bosman

unread,
Nov 30, 2009, 7:44:52 AM11/30/09
to

Thank's adding 'component' to the searchfields in whine.pl worked.
After I did that i can use [% bug.component %] in the mail template.

Rogier

CJ-77

unread,
Dec 16, 2009, 5:28:52 PM12/16/09
to support-...@lists.mozilla.org

I added 'bugs.component' to my @searchfields in the whine.pl.

I added <th align="left">Component</th> in the whine\mail.html.tmpl.
I also added <td align="left">[% bug.component FILTER html %]</td> in the
whine\mail.html.tmpl.

However, when I receive my whine emails, all I see is the Component header.

I'm missing something and not exactly sure. Thank you in advance for your
assistance.


--
View this message in context: http://old.nabble.com/bugzilla-whine-email.txt.tmpl-tp26495595p26819626.html
Sent from the Bugzilla - Users mailing list archive at Nabble.com.

CJ-77

unread,
Dec 16, 2009, 6:00:26 PM12/16/09
to support-...@lists.mozilla.org

GOAL: Add Component column to whine emails to show component name for
associated bugs.

I added 'bugs.component_id' to my @searchfields in the whine.pl.

I added <th align="left">Component</th> in the whine\mail.html.tmpl.

I also added <td align="left">[% bug.component_id FILTER html %]</td> in
the whine\mail.html.tmpl.

However, when I receive my whine emails, all I see is the Component header &
Component ID. I'm missing the mapping piece to the component name. Can
someone assist me with what is needed?
--
View this message in context: http://old.nabble.com/bugzilla-whine-email.txt.tmpl-tp26495595p26820045.html

Eric Black

unread,
Dec 17, 2009, 11:30:03 AM12/17/09
to support-...@lists.mozilla.org

> GOAL: Add Component column to whine emails to show component name for
> associated bugs.
>
> I added 'bugs.component_id' to my @searchfields in the whine.pl.
>
> I added <th align="left">Component</th> in the whine\mail.html.tmpl.
> I also added <td align="left">[% bug.component_id FILTER html %]</td> in
> the whine\mail.html.tmpl.
>
> However, when I receive my whine emails, all I see is the Component header &
> Component ID. I'm missing the mapping piece to the component name. Can
> someone assist me with what is needed?


Yes, you need to do the mapping with 'map_components.name' in Bugzilla/Search.pm. Add that to the search parameters in whine.pl and then reference it as bug.map_components.name. Use map_assigned_to.login_name, which is already in the stock whine scripts, as an example.

0 new messages