happy bmo push day!

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

• [860723] Custom fields are shown twice in report axis selectors
• [861528] $user->can_enter_product() now returns the product object instead of 1
• [782210] If a custom field depends on a product, component or classification, the “mandatory” bit is ignored on bug creation
• [858911] Oracle fails with “ORA-04043: object T_GROUP_CONCAT does not exist” when installing Bugzilla for the first time
• [855549] Project Kickoff Form: Dependent bugs weren’t created from form
• [859315] lots of “Lock wait timeout exceeded” errors when updating cf_crash_signature
• [750170] switch from arecibo to sentry for error reporting
• [841633] Project Kickoff Form: CC sub-bug owners into main project tracker bug
• [841440] Project Kickoff Form: Remove Several Questions
• [864499] adding “due date” to the Marketing Product.
• [864200] use text/plain mime type for attachments with a .lang extension
• [828344] “contains all of the words” no longer looks for all words within the same comment or flag
• [864304] Requesting needinfo from more than one person is annoying
• [715148] Increase the attachment size limit to 10meg
• [859534] “Find product” field at BMO/describecomponents.cgi?full=1 can’t find “bugzilla.mozilla.org :: User Interface”
• [853483] Triage report times out on Firefox (Any) query

happy bmo push day!

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

• [860657] ‘Illegal division by zero’ on product dashboard when the product has zero bugs
• [860797] add product dashboards to robots.txt
• [848240] Mozilla theme doesn’t show visited link coloring.
• [861392] Be more descriptive about “Ignore Bug Email”
• [861414] In form.mdn, add link to “Switch to the advanced bug entry form”
• [836006] Need Bug Template for Partners Bug Submissions

happy bmo push day!

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

• [855846] sanitizeme.pl should disable email for all users as well as filter the email address
• [852750] Flags requested of me, shows only requested flags in non-restricted bugs
• [856869] New Product: Firefox Health Report
• [853892] “Internet Public Policy” new bug form
• [793958] Need a Bugzilla Swag Request Form Deleted
• [855549] Project Kickoff Form: Dependent bugs weren’t created from form
• [859598] Autocomplete suggests inactive/disabled accounts as matches
• [859313] lots of “Lock wait timeout exceeded” errors when updating TagNewUser’s comment_count
• [859480] Ability to ignore specific bugs (not get email from them, even as the reporter)
• [852279] Bug pages no longer added to bfcache due to unload listener on Window
• [859406] syncmsandversions.pl doesn’t copy the isactive field
• [859206] bugzilla etiquette should direct people to ask #bmo to take action
• [850723] saved searches on my dashboard disappear from time to time
• [855258] The dependency graph always uses urlbase, even when sslbase is in use
• [857562] ajax_user_autocompletion param ignored on Search by People fields
• [355620] Lines enclosed in <simplelist> do not wrap in the PDF version of the Bugzilla Guide

i’d like to draw attention to dkl’s work on bug 148564 – you can now tell bugzilla to never email you about specific bugs, even if you’re the reporter:

[a-team] conversations with face

face is an irc bot i run on the #ateam channel.
its responses are purely random, drawing from past conversations on channel.

[16:46] <mdas> face: markov
[16:46] <face> tries again salivates takes code to the holiday with a great
[16:46] <mdas> hahaha
[16:46] <mcote> a great what??
[16:46] <mcote> face don’t leave me hanging
[16:46] * face never wrote it down apparently
[16:47] <mdas> HAHA
[16:47] <mcote> HA

happy bmo push day!

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

• [850639] the dependency graph should have an upper limit on the number of nodes it attempts to graph
• [856110] Add a review link to the dashboard for review attachment flags
• [856706] Please update metrics permissions / BMO grant script
• [855656] Hide/disable the tracking-thunderbird-esr10 flags
• [855626] release tracking flag refresh (23)
• [856936] Update Mozilla Project Review form to use the sec-review? flag instead of the sec-review-needed keyword
• [853886] New “Internet Public Policy” product and components
• [856869] New Product: Firefox Health Report
• [724048] Instant search doesn’t work in Fennec Native product
• [852560] Bugzilla cannot be installed with MySQL 5.6, because the have_innodb variable no longer exists (“InnoDB is disabled in your MySQL installation”)
• [854074] Remove all references to the uwinnipeg.ca PPM repository as it is no longer available

happy bmo push day!

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

• [854322] Use of uninitialized value in Bugzilla/Extension/Push/Serialise.pm line 131
• [854386] needinfo doesn’t work if user confirmation is required
• [848583] Use of uninitialized value in subroutine entry at /data/www/bugzilla.mozilla.org/Bugzilla/BugMail.pm line 408.
• [854412] search plugin does not use bmo favicon but the generic dino head
• [838846] In Product.get, include_fields => ['components'] no longer returns data about components
• [854770] “Wide character in subroutine entry” error in TCL connector
• [854901] backport bug 850986 to bmo: don’t allow setting a flag’s requestee to a disabled account
• [852795] Request emails should include X-Bugzilla-Product, etc headers (fully backport upstream bug 573919)
• [855128] defer loading of persona
• [855144] “Android Background Services” product
• [855414] Editing of FlagTypeComment values for each status is broken due to the 4.2 upgrade
• [841419] Project Kickoff Form: Wording Changes
• [855073] Add information to needinfo email

happy bmo push day!

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

• [853328] product/component searching should also search the product’s description.
• [853451] “not implemented” error when updating a bug with the “locale” multi-select field visible
• [853432] “Flags requested of you” doesn’t show flags that are requested on Resolved bugs
• [849905] bug filing links in my dashboard should be able to be opened in new tabs/windows
• [853913] Some MyDashboard “updated” friendly dates are inappropriate and/or broken w.r.t. timezones
• [849120] change “send error to error reporter” from forking to running a process

happy bmo push day!

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

• [851818] Modernize the entry page for filing a bug by including, keeping, and removing products shown on the enter bug page
• [853034] unable to set tracking fields when editing multiple bugs
• [853314] unable to edit bugzilla push options – insecure dependency
• [833204] add support for sending attachments via push

happy bmo push day!

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

• [850126] token id defined twice on logged out pages
• [849721] high memory consumption on scl3 bmo webheads
• [848457] TypeSniffer is chopping the first 32 bytes from attachments
• [847448] Add url field (bug_file_loc) to form.doc
• [850675] editing the splinter url always appends a /, which results in a broken url
• [852022] persona throwing the error: you cannot combine the navigator.id.watch() API with navigator.id.getVerifiedEmail() or navigator.id.get()
• [852026] persona should have a timeout on the connection to the verification server
• [851480] Swag bugs do not have an XML attachment anymore

bugzilla.mozilla.org upgraded to v4.2

highlights from the bugzilla 4.2 upgrade:

changes to bugzilla search

bugzilla’s searching mechanics got a complete rewrite between 4.0 and 4.2.  see this blog post for more details.

dashboards

david lawrence [:dkl] has worked hard on bringing user and product dashboards to bmo, and has done an amazing job.

• user dashboard
• product dashboard

create attachments from the clipboard

you can now create attachments by pasting content into a text field.

restricted commenting

some bug reports are inundated with comments that make it difficult for developers to conduct technical discussions.
restricting comments provides the ability for users in the editusers group to prevent users who are not in the editbugs from making additional comments.

guidelines

• restrictions may be applied to bugs which are subject to high volumes of off topic comments, or bugs which contain high volumes of violations of bugzilla etiquette guidelines.
• restrictions should not be used as a preemptive measure against comments which have not yet occurred.
• restrictions should not be used to privilege editbugs users over other users in valid disputes/discussions.

impact

• users who are not in the editbugs group will not be able to comment on the bug, nor will they be able to change the value of any field.
• all users will still be able to CC themselves to the bug.
• all users will still be able to vote for the bug.