happy bmo push day!

the following changes have been pushed to bugzilla.mozilla.org:

  • [1059627] changes made at the same time as a comment are no longer grouped with the comment
  • [880097] Only retrieve database fetched values if requested
  • [1056162] add bit.ly support to bmo
  • [1059307] Remove reporting of the firefox release channel from the guided bug entry (hasn’t been accurate since firefox 25)

discuss these changes on mozilla.tools.bmo.

bitly

happy bmo push day!

the following changes have been pushed to bugzilla.mozilla.org:

  • [1058479] move the “mozilla employees” warning on bugzilla::admin next to the submit button
  • [1058481] git commits should link to commitdiff not commit
  • [1056087] contrib/merge-users.pl fails if there are no duplicate bug_user_last_visit rows
  • [1058679] new bug API returning a ref where bzexport expects bug data
  • [1057774] bzAPI landing page gives a 404
  • [1056904] Add “Mentored by me” to MyDashboard
  • [1059085] Unable to update a product’s group controls: Can’t use string (“table”) as an ARRAY ref while “strict refs” in use
  • [1059088] Inline history can be shown out-of-order when two changes occur in the same second

discuss these changes on mozilla.tools.bmo.

happy bmo push day!

the following changes have been pushed to bugzilla.mozilla.org:

  • [1058274] The input field for suggested reviewers when editing a component needs ‘multiple’ to be true for allowing for more than one username
  • [1051655] mentor field updated/reset when a bug is updated as a result of a change on a different bug (eg. see also, duplicate)
  • [1058355] bugzilla.mozilla.org leaks emails to logged out users in “Latest Activity” search URLs

discuss these changes on mozilla.tools.bmo.

happy bmo push day!

the following changes have been pushed to bugzilla.mozilla.org:

  • [1047405] Comment tagging GUI not fully localizable because of text in Javascript instead of template
  • [1048712] comment tagging suggestions always returns a single result
  • [1054795] remove ‘Bugzilla Data For Researchers’ link
  • [1050230] Use better icons for the guided bug entry product selection to differentiate Fx, Fx for Android and FxOS
  • [1022707] Duplicate review flags on attachments in Toolkit and Firefox for Metro
  • [1050628] flag state API doesn’t honour bug or attachment security
  • [1055945] splinter generates “Use of uninitialized value” warnings when dealing with public reviews on private attachments

discuss these changes on mozilla.tools.bmo.

happy bmo push day!

the following changes have been pushed to bugzilla.mozilla.org:

  • [1049929] Product Support / Corp Support to Business Support
  • [1033897] Firefox OS MCTS Waiver Request Submission Form
  • [1041964] Indicate that a comment is required when selecting a value which has an auto-comment configured
  • [498890] Bugzilla::User::Setting doesn’t need to sort DB results
  • [993926] Bugzilla::User::Setting::get_all_settings() should use memcached
  • [1048053] convert bug 651803 dupes to INVALID bugs in “Invalid Bugs” product

discuss these changes on mozilla.tools.bmo.

happy bmo push day!

the following changes have been pushed to bugzilla.mozilla.org:

  • [938272] Turn on Locale multi-select field in Mozilla Localizations :: Other
  • [1046779] Components with no default QA still display a usermenu arrow on describecomponents.cgi
  • [1047328] Please remove “Firefox for Metro:” from the “https://bugzilla.mozilla.org/enter_bug.cgi” page
  • [1047142] The User Story field should be expanded/editable by default if it’s non-empty when cloning a bug
  • [1047131] enable “user story” field on all products
  • [1049329] fix width of user_story field, and hide label for anon access when no story is set
  • [1049830] Bug.search with count_only = 1 does not work for JSONRPC and REST but does work for XMLRPC

discuss these changes on mozilla.tools.bmo.

happy bmo push day!

the following changes have been pushed to bugzilla.mozilla.org:

  • [1039198] Field name is still “Bug #” for the Bug Created field
  • [922482] Change all bugs with general@js.bugs assignee to nobody@mozilla.org
  • [713307] Please add FlagTypeComments for tracking/approval flags
  • [1037571] Change Several Bugs at Once Does Not Allow Modification of the QA Whiteboard
  • [1032883] update FlagDefaultRequestee extension to use object hooks
  • [1040580] Bugzilla detects Firefox OS device as Hardware:Other, OS:Other
  • [1026416] “blocks” field is present as empty string when empty, rather than null or []
  • [1040841] Provide good error message when people can’t use form.legal
  • [1041538] A few more “Bugmail filtering” fields need to be excluded from the prefs UI
  • [1041559] “Please wait while your bugs are retrieved” shown above menu header for search error pages
  • [936468] Move OS: Windows 8 Metro to Windows 8.1

discuss these changes on mozilla.tools.bmo.

happy bmo push day!

switching the default monospace font on bmo yesterday highlighted a few issues with the fira-mono typeface that we’d like to see addressed before we use it.  as a result comments are now displayed using their old font.

the following changes have been pushed to bugzilla.mozilla.org:

discuss these changes on mozilla.tools.bmo.

happy bmo push day!

the following changes have been pushed to bugzilla.mozilla.org:

  • [1029500] bug.attachments shouldn’t include attachment data by default
  • [1032323] canonicalise_query() should omit parameters with empty values so generated URLs are shorter
  • [1027114] When sending error to Sentry for webservice failures, we need to first scrub the username/login/password from the query string
  • [1026586] Using Fira as default font in Bugzilla
  • [1027182] merge-users.pl – SQL to remove bug_user_last_visit not correct
  • [1036268] REST webservice should return http/404 for invalid methods
  • [1027025] comment.creator has no real_name
  • [1036795] comment.raw_text is returned by the bzapi compatibility extension
  • [1036225] Return a link to the REST documentation in “method not found” errors
  • [1036301] change the description of the “bug id” field on bugmail filtering preferences tab to “new bug”
  • [1028269] Firefox OS Pre-load App Info Request Form
  • [1036303] add a list of tracking/project/etc tracking flags to the bugmail filtering prefs page

discuss these changes on mozilla.tools.bmo.

using “bugmail filtering” to exclude notifications you don’t want

a common problem with bugzilla emails (aka bugmail) is there’s too much of it.  if you are involved in a bug or watching a component you receive all changes made to bugs, even those you have no interest in receiving.

earlier this week we pushed a new feature to bugzilla.mozilla.org : bugmail filtering.

bugmail_filtering

this feature is available on the “bugmail filtering” tab on the “user preference” page.


 

there are many reasons why bugzilla may send you notification of a change to a bug:

  • you reported the bug
  • the bug is assigned to you
  • you are the qa-contact for the bug
  • you are on the cc list
  • you are watching the bug’s product/component
  • you are watching another user who received notification of the bug
  • you are a “global watcher”

dealing with all that bugmail can be time consuming.  one way address this issue is to use the x-headers present in every bugmail to categorise and separate bugmail into different folders in your inbox.  unfortunately this option isn’t available to everyone (eg. gmail users still cannot filter on any email header).

bugmail filtering allows you to tell bugzilla to notify you only if it’s a change that you’re interested in.

for example, you can say:

don’t send me an email when the qa-whiteboard field is changed unless the bug is assigned to me

  filter-qa

if multiple filters are applicable to the same bug change, include filters override exclude filters.  this interplay allows you to write filters to express “don’t send me an email unless …”

don’t send me an email for developer tools bugs that i’m CC’ed on unless the bug’s status is changed

  • first, exclude all developer tools emails:

filter-devtools-exclude

  • then override the exclusion with an inclusion for just the status changes:

filter-devtools-include

Follow

Get every new post delivered to your Inbox.

Join 88 other followers