happy bmo push day!

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

  • [994570] unable to create an attachment with review+ : “You must provide a reviewer for review requests”
  • [994540] “details” link in overdue requests email links to attachment content instead of details page
  • [993940] Group icons should be displayed for indirect memberships, too
  • [993913] remove the %user_cache from inline history, and ensure the object cache is always used
  • [998236] Privacy policy url has changed
  • [968576] Dangerous control characters allowed in Bugzilla text
  • [997281] New QuickSearch operators can short-circuit each other depending on which ones are tested first
  • [993894] the database query in bless_groups is slow
  • [936509] Automatically disable accounts based on the number of comments tagged as spam
  • [998017] Internal error: “Not an ARRAY reference” when using the summarize time feature
  • [999734] User email addresses are publicly visible in profile titles
  • [993910] Bugzilla/Search/Saved.pm:294 isn’t using the cache
  • [998323] URLs pasted in comments are no longer displayed

discuss these changes on mozilla.tools.bmo.

happy bmo push day!

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

  • [924265] add an alert date field/mechanism to the “Infrastructure & Operations” product
  • [987765] Updates to Developer Documentation product’s “form.doc” form and configuration
  • [891757] “Additional hours worked” displayed inline with comments is now superfluous
  • [986590] Confusing error message when not finding reviewer
  • [987940] arbitrary product name (text) injection in guided workflow
  • [988175] Needinfo dropdown should include “myself”
  • [961843] Reset password token leakage
  • [984505] Link component and product to browse for other bugs in this category
  • [987521] flag activity api needs to prohibit requests which return the entire table
  • [990982] Use <optgroup/> to group products into classifications in the product drop-down on show_bug.cgi
  • [991477] changing a tracking flag’s value doesn’t result in the value being updated on bugs
  • [988414] The drop down menu icon next to the user name is not visible in Chrome on Mac OSX
  • [994467] remove “anyone” from the needinfo menu

discuss these changes on mozilla.tools.bmo.

happy bmo push day!

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

  • [880113] Use the cache for the product and component name
  • [988744] orangefactor template_before_process should check $file before checking user settings
  • [989415] Weird “0 of attachment” text in bugmail from patches attached to security bugs
  • [987741] deleted comment checking runs before tags are preloaded, triggering excessive database queries
  • [989650] Allow requestees to set attachment flags even if they don’t have editbugs privs
  • [990070] Bug.update_attachment should allow for adding a comment when updating attachment details similar to attachment.cgi
  • [989633] Unable to change content type using Bug.update_attachment if attachment previously set to is_patch = 1
  • [774198] “Undefined subroutine Fh::slice” while attaching a file

discuss these changes on mozilla.tools.bmo.

happy bmo push day!

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

  • [901599] changing the requestee of a pending needinfo flag should redirect the request rather than clearing it
  • [983963] Add ability to make any bug in product Audio/Visual Infrastructure -> Confidential Mozilla Employee Bug or Infrastructure-related Bugs
  • [985305] update the metrics elasticsearch reporter to bypass es node discovery
  • [983045] Change the word “outstanding” in the request nagger emails to “overdue”
  • [986124] Allow people to set “See Also” when filing/creating/entering a bug on enter_bug.cgi or the Bug.create webservice
  • [978773] API to query flag history by user

discuss these changes on mozilla.tools.bmo.

happy bmo push day!

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

  • [960830] Update Brand Engagement Initiation Form
  • [982788] Linkify the output of “git push” in bug comments
  • [905555] S/MIME help talks only about openssl where Thunderbird GUI would work also
  • [981937] Bugzilla reports “-1″ notifications
  • [983549] changes to the profiles table in token.cgi are not clearing memcached entries

discuss these changes on mozilla.tools.bmo.

happy bmo push day!

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

  • [977981] add the “Preview” mode for attachment comments
  • [977505] Make the dashboard white-on-red counter easier to click
  • [975195] “Your Outstanding Requests” emails don’t include superreview requests
  • [956229] develop a system to track the lifetime of review/feedback/needinfo requests
  • [926962] all tracking flags are visible on the ‘change many bugs at once’ page
  • [977761] Create product and affiliations for Intellego project
  • [978941] grammar issue
  • [916633] join_activity_entries doesn’t reconstitute text with commas correctly.
  • [966180] enable USE_MEMCACHE on most objects
  • [956230] improve instrumentation of bugzilla’s internals
  • [979092] changing timezone breaks MyDashboard
  • [979727] increase the mod_perl sizelimit to 700_000 on production
  • [979411] Fix content-type for woff files
  • [977137] Comment and Preview tabs need accessibility markup
  • [977523] Comment textarea has padding:0
  • [980056] ReferenceError: REVIEW is not defined page.cgi javascipt error when viewing a patch in Splinter
  • [979431] Please rename Talkilla product to Loop and update User Stories extension

discuss these changes on mozilla.tools.bmo.

happy bmo push day!

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

  • [975204] Comment Preview tabs broken in New bug page
  • [976765] add hooks to Bugzilla/WebService/Server/REST.pm
  • [976796] Spelling mistakes in Bugzilla/WebService/Bug.pm
  • [977238] Compress CSS files

discuss these changes on mozilla.tools.bmo.

happy bmo push day!

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

  • [974946] [edit] action is showing up multiple times on the first comment
  • [975546] Missing description in the “Bug Fields” page for “Importance”
  • [975943] add special support for a “deleted” comment tag

discuss these changes on mozilla.tools.bmo.

happy bmo push day!

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

  • [972349] comment preview is in an incorrect location when creating a bug using the advanced bug entry form, sandstone skin, and a wide window.
  • [972982] Enable “user-story” editing for Talkilla product
  • [966676] The ‘sudo’ cookie should not be accessible from JavaScript
  • [973582] Don’t link “UUID <id>” to crash-stats
  • [785565] Search by change history between two dates doesn’t give expected result
  • [973766] user profile should count reviewboard url attachments as patches
  • [963195] Need field added on gear/budget request form to designate if this is a Firefox Student Ambassador event
  • [971004] Bugzilla form for Community IT Requests
  • [941671] Rename “mozilla-corporation-confidential” to “mozilla-employee-confidential” and update membership accordingly
  • [974393] comment tag link is collapsing all comments including those with the tag

discuss these changes on mozilla.tools.bmo.

markup within bugzilla comments

a response i received multiple times following yesterday’s deployment of comment previews on bugzilla.mozilla.org was “wait, bugzilla allows markup within comments now?”.

yes, and this has been the case for a very long time.  here’s a list of all the recognised terms on bugzilla.mozilla.org;

  • bug number
    • links to the specified bug, if it exists. the href’s tooltip will contain the information about the bug
    • eg. “bug 40896″
  • attachment number
    • links to the specified attachment, if it exists. the href’s tooltip will contain the information about the attachment
    • adds action buttons for [diff][details][review]
    • eg. “attachment 8374664″
  • comment number
    • links to a comment in the current bug. “comment 0″ will link to the bug’s description
    • eg. “comment 12″
  • bug number comment number
    • links to a comment in another bug.
    • eg. “bug 40896 comment 12″
  • email addresses
    • linkified into a mailto: href
    • eg. “glob@mozilla.com”
  • bp-crash-id
    • links to the crash-stats for the specified crash-id
    • eg. “bp-56630b1a-0913-4b4e-b701-d96452140102″
  • CVE-number or CAN-number
    • links to the cve/can security release information on cve.mitre.org
    • eg. “CVE-2013-1733″
  • rnumber
    • links to a svn.mozilla.org revision number
    • eg. “r1234″
  • bzr commit messages
  • git commit messages
    • links to the revision on git.mozilla.org
    • see example here (only the last two lines of the commit message are required)
  • hg changesets: repository changeset revision
    • links to the changeset on hg.mozilla.org
    • eg. “mozilla-inbound changeset c7802c9d6eec”
Follow

Get every new post delivered to your Inbox.

Join 75 other followers