happy bmo push day!

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

  • [798271] Create the L20n product
  • [799257] Backport bug 795650 and bug 797883 to bmo/4.0 and bmo/4.2 for performance improvement
  • [798367] The element focused after pressing in a comment box should be the “submit comment” button.
  • [800691] for Thunderbird product, change guided bug entry form default component to Untriaged
  • [795980] Changes in REMO budget request form

coming attraction: comment tagging

i’ve been working on a bugzilla enhancement which allows you to tag individual comments with arbitrary strings.

it’s tracked in bug 793963, currently waiting for review, and will be back-ported to bugzilla.mozilla.org.

comment tagging features:

automatic collapsing of comments

the bugzilla administrator can configure a list of comment tags which will result in those comments being collapsed by default when a bug is loaded.

this allows obsolete or irrelevant comments to be hidden from the information stream.

comment grouping/threading

bugzilla will show a list of all comment tags in use on the bug, and clicking on a tag will expand those comments while collapsing all others.

this allows for simple threading of comments without diverging significantly from the current bugzilla user interface, api, and schema. you’ll be able to tag all comments relating to the same topic, and remove comments no longer relevant to that thread by removing the tag.

highlighting importing comments

on bugs with a lot of information, it can be time consuming for people not directly involved in the bug to find the relevant comments.  applying comment tags to the right comments assists this, and may negate the need for information to be gathered outside of bugzilla.

for example:

    • tagging a comment with “STR” (steps to reproduce) will help the qa team quickly find the information they need to verify the fix
    • writing a comment summarising a new feature and tagging it with “docs” will help the generation of documentation for mdn or similar

implementation notes

  • the “add tag” input field has an auto-complete drop-down, drawing from existing tags weighted by usage count
  • by default editbugs membership is required to add tags to comments
  • comment tags are not displayed unless you are logged in to bugzilla
  • tags are added and removed via xhr, changes are immediately visible to the changer without refreshing the page
  • tagging comments will not trigger bugmail, nor alter a bug’s last-modified date
  • tags added by other users (or on other tabs) will generally not be visible without a page refresh

happy bmo push day!

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

  • [797872] Grammatical mistake on Instant Search
  • [799005] release tracking flag refresh (19)
  • [797934] Create a new bugzilla product for Metro Firefox
  • [799545] Need status-firefox-n flags for boot2gecko product
  • [757935] Bugs with resolution MOVED cannot be edited
  • [790909] Editing dependencies from the “Change Several Bugs at Once” page does not work as expected (bug IDs are incorrectly parsed)
  • [764459] Bug submission form: Privacy > Data release proposal

bugzilla.mozilla.org integration best practices

an excerpt from https://wiki.mozilla.org/BMO/Integration_Best_Practice

  • Do not poll more frequently than every 5 minutes
    • Seriously, you don’t need to poll every minute
  • Ask for bugs updated since your last poll, or track a bug’s last modified date
    • If your system is polling for bugs, you should ask BMO for bugs updated since your last poll
    • The chfieldfrom argument will accept times as well as dates (eg. “2012-10-08 01:30”)
    • Search results generally return a bug’s last-modified date; there’s no need to re-request the bug if it hasn’t been modified since the last time you saw it
  • Only request the fields that you are interested in
    • By default all APIs return more information than you probably require – use the include_fields parameter to specify the exact fields you need (BzAPI)(XMLRPC/JSONRPC)
    • When searching with BzAPI, avoid specifying non-bold columns if you can avoid it, because it’ll be slower and user server-side resources
  • Coalesce queries where possible
    • If you have multiple bugs, components, etc to query, it can be more efficient issue a single request rather than iterating over your list and issuing multiple requests

information about the “needinfo” flag

a few notes about the needinfo flag which was added to bugzilla.mozilla.org last week, and enabled across all products today:

  • with a few minor exceptions, it’s a normal bugzilla flag
    • searching, mail notifications, etc, all function like any other flag
    • you can use the “requests” page to search for bugs with this flag set
  • if the requestee comments on the bug, the needinfo flag is automatically cleared
  • you can’t set the flag to + or – .. either will result in the flag being cleared

happy bmo push day!

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

  • [677081] Private comments should remain visible by their author
  • [791137] Last line of last file is not shown in Splinter if there is no newline at the end of the patch
  • [783091] Missing links when there are multiple ‘review?(foo)’ shown in attachment box on show_bug.cgi
  • [786532] Modified clicks on email links are intercepted
  • [794080] guided bug entry throws a “cannot focus invisible element” error on IE8
  • [796043] Inline history eats your comment if you quote a duplicated bug
  • [797376] On editparams.cgi, spelling mistake in Splinter Patch Review section
  • [790697] Profanivore causes broken HTML main by creating very long lines
  • [713796] “Reset Assignee to default” and “Reset QA Contact to default” should only be checked when the assignee/qa-contact is the default
  • [264721] create READY state for bugs which have enough info/testcases to start work