Thanks for all your suggestions.
We have communicated this problem with members this morning.
We told them that not to add unsuitable [foobar] on the bug summary if
they are not sure which one is correct.
Also, timely modification is necessary if the [foobar] is inappropriate.
The key point is making the bug summary as possible as clear.
If you have better suggestions, please feel free to let us know.
Sorry for any inconvenience!
Have a nice day.
Cheers,
William
On 09/15/2015 11:37 PM, 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
dev-fxos@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-fxos
_______________________________________________
dev-fxos mailing list
dev-fxos@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-fxos
