I agree with Ben.  [Aries] or [Flame] is necessary per device specific
issues.  [Lockscreen] isn't needed for lockscreen bugs.

In addition, [New Homescreen] is used for the new homescreen versus old
homescreen.  There's a few other cases of comparison.  It makes it easier
for the Dev working on it to determine if it's a new homescreen or old
homescreen issue.

On Wed, Sep 16, 2015 at 1:52 AM, Frederik Braun <[email protected]> wrote:

> FWIW, Bugzilla sends extra email headers like X-Bugzilla-Component,
> X-Bugzilla-Status. There's a Thunderbird extension called "Mnenhy" which
> you can set up to show them just beneath the other headers (Subject,
> Date, …).
>
>
>
>
>
> On 15.09.2015 17:37, Benjamin Smedberg wrote:
> >
> >
> > On 9/15/2015 11:24 AM, Tim Guan-tin Chien wrote:
> >> Hi,
> >>
> >> I often seeing bug unrelated to the UI or the specific UI being marked
> >> with a [..] pointing to the UI. Like
> >>
> >> [Lock Screen]Can't open a missed call from lockscreen notification.
> >>
> >> Which is actually a Dialer regression*. We have Bugzilla components, I
> >> think the summary line tag is confusing and should be avoided.
> >>
> >> If people agree we should ask our outsourcing QA avoiding file bug
> >> with that kind of summary.
> >
> > The subject of bugzilla email notifications doesn't include the
> > product/component information. I recommend being practical about this
> > and making the bug summary as descriptive as necessary so that people
> > reading bugmail are clear.
> >
> > So for instance, often times somebody will file a bug in Firefox
> > desktop: "Flash doesn't repaint properly when scrolling". After a little
> > investigation, we'll discover that this is a problem only for windowless
> > Flash on win64, so then I will clarify the bug summary: "Windowless
> > Flash+win64: Flash doesn't repaint properly on scroll".
> >
> > In this particular case, I think the bug summary is clear enough without
> > the [Lock screen] marker, but that may depend on the specifics.
> >
> > --BDS
> >
> > _______________________________________________
> > dev-fxos mailing list
> > [email protected]
> > https://lists.mozilla.org/listinfo/dev-fxos
>
> _______________________________________________
> dev-fxos mailing list
> [email protected]
> https://lists.mozilla.org/listinfo/dev-fxos
>
_______________________________________________
dev-fxos mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-fxos

Reply via email to