bugzilla.mozilla.org’s new look

this quarter i’ve been working on redesigning how bugs are viewed and edited on bugzilla.mozilla.org — expect large changes to how bmo looks and feels!

unsurprisingly some of the oldest code in bugzilla is that which displays bugs; it has grown organically over time to cope with the many varying requirements of its users worldwide.  while there has been ui improvements over time (such as the sandstone skin), we felt it was time to take a step back and start looking at bugzilla with a fresh set of eyes. we wanted something that was designed for mozilla’s workflow, that didn’t look like it was designed last century, and would provide us with a flexible base upon which we could build further improvements.

a core idea of the design is to load the bug initially in a read-only “view” mode, requiring the user to click on an “edit” button to make most changes. this enables us to defer loading of a lot of data when the page is initially loaded, as well as providing a much cleaner and less overwhelming view of bugs.

bug-modal-1

major interface changes include:

  • fields are grouped by function, with summaries of the functional groups where appropriate
  • fields which do not have a value set are not shown
  • an overall “bug summary” panel at the top of the bug should provide an “at a glance” status of the bug

the view/edit mode:

  • allows for deferring of loading data only required while editing a bug (eg. list of all products, components, versions, milestones, etc)
    • this results in 12% faster page loads on my development system
  • still allows for common actions to be performed without needing to switch modes
    • comments can always be added
    • the assignee can change the bug’s status/resolution
    • flag requestee can set flags

bug-modal-2

you can use it today!

this new view has been deployed to bugzilla.mozilla.org, and you can enable it by setting the user preference “experimental user interface” to “on”.

you can also enable it per-bug by appending &format=modal to the url (eg. https://bugzilla.mozilla.org/show_bug.cgi?id=1096798&format=modal).  once enabled you can disable it per-bug by appending &format=default to the url.

what next?

there’s still a lot to be done before there’s feature parity between the new modal view and the current show_bug.  some of the major items missing with the initial release include:

  • cannot edit cc list (cannot remove or add other people)
  • comment previews
  • comment tagging (existing tags are shown, cannot add/delete tags)
  • cc activity is not visible
  • bulk comment collapsing/expanding (all, by tag, tbpl push bot)
  • alternative ordering of comments (eg. newest-first)
  • bmo show_bug extensions (eg mozreview, orange factor, bounty tracking, crash signature rendering)

you can view the complete list of bugs, or file a new bug if you discover something broken or missing that hasn’t already been reported.

happy bmo push day!

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

  • [1146806] “new bug” menu has literal “…” instead of a horizontal ellipsis
  • [1146360] remove the winqual bug entry form
  • [1147267] the firefox “iteration” and “points” fields are visible on all products
  • [1146886] after publishing a review with splinter, the ‘edit’ mode doesn’t work
  • [1138767] retry and/or avoid push_notify deadlocks
  • [1147550] Require a user to change their password if they log in and their current password does not meet the password complexity rules
  • [1147738] the “Rank” field label is visible when editing, even if the field itself isn’t
  • [1147740] map format=default to format=__default__
  • [1146762] honour gravatar visibility preference
  • [1146910] Button styles are inconsistent and too plentiful
  • [1146906] remove background gradient from assignee and reporter changes
  • [1125987] asking for review in a restricted bug doesn’t work as expected (“You must provide a reviewer for review requests” instead of “That user cannot access that bug” error)
  • [1149017] differentiate between the bug’s short-desc and the bug’s status summary in the header
  • [1149026] comment/activity buttons are not top-aligned
  • [1141770] merge_users.pl fails if the two accounts have accessed the same bug and is in the bug_interest table
  • [972040] For bugs filed against Trunk, automatically set ‘affected’ release-tracking flags
  • [1149233] Viewing a bug with timetracking information fails: file error – formattimeunit: not found
  • [1149390] “duplicates” are missing from the modal view
  • [1149038] renaming a tracking flag isn’t clearing a memcached cache, resulting in Can’t locate object method “cf_status_thunderbird_esr39″ via package “Bugzilla::Bug” errors

discuss these changes on mozilla.tools.bmo.

happy bmo push day!

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

  • [1145502] cf_crash_signature missing in fresh BMO install
  • [1145689] Adding “Content Services” into Key Initiatives
  • [1146219] the ‘abuse’ comment tag should function like the ‘abusive’ tag and trigger automatic account disabling
  • [1141165] Enforce mandatory field on form.reps.mentorship
  • [1146434] renaming of “Distribution/Bundling” component broke one of the project kickoff form’s sub-bugs
  • [1096798] prototype modal show_bug view

discuss these changes on mozilla.tools.bmo.

happy bmo push day!

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

  • [1139872] The URL in bugmail microdata has the ‘#’ URI encoded, causing the links to break
  • [1140764] “suggested reviewers” menu overflows from visible area if there are many reviewers.
  • [1141440] OPTION response for CORS requests to REST doesn’t allow X-Bugzilla headers
  • [1143160] A review comment on bug 1131776 breaks splinter
  • [1141452] Adjustment on the project flags (blocking-b2g and tracking-b2g)
  • [1142399] invalid xmlrpc requests warns: Use of uninitialized value $file in substitution (s///) (Bugzilla/WebService/Server/XMLRPC.pm:114)
  • [1132963] Automatically detect and redirect to Google doc URLs (akin to github-pr and rb handling)
  • [1143536] product dashboard doesn’t honour product visibility
  • [1143753] Update to Mozilla Recruiting Requisition Opening Process Template

discuss these changes on mozilla.tools.bmo.

happy bmo push day!

  • [1138541] Updating lists on Gear Request form
  • [1137368] Allow the bug’s assignee to edit attachment fields, even if they do not have editbugs
  • [1102428] Custom field for MozReview link, with dynamic info
  • [1139939] “BadResponse: ‘Location’ header missing from 201 Created response” when commenting with bztools
  • [1140203] Component name adjustment ‘Marketplace:Pre-Installed Apps’
  • [1140966] allow cookie+api-token GET REST requests
  • [1140458] Allow API authentication with X-Headers
  • [1140234] extend review/flag_activity to allow filtering by status and bug_id
  • [1140798] Possible client side code injection in “suggested reviewers” menu.
  • [1140049] Add a note about MozReview to the Create Attachment page
  • [1140215] 3rd Party Applications Issue Form
  • [1137080] add an indicator to the user profile page if the user has canconfirm or editbugs rights
  • [1003701] add the ability for users to prevent review/feedback/needinfo requests
  • [1139749] Bugzilla shouldn’t try to write API tokens into the shadow DB
  • [1139872] The URL in bugmail microdata has the ‘#’ URI encoded, causing the links to break

 

bugzilla now shows the status of mozreview hosted reviews:

moz-review

it’s now possible to prevent review, feedback, and needinfo requests:

block review requests

discuss these changes on mozilla.tools.bmo.

happy bmo push day!

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

  • [1134392] Need edits to Recruiting Component
  • [1136222] Adding “Rank” to Product:Core Component: webRTC, webRTC: Audio/Video, webRTC: Signaling, webRTC: Networking
  • [1136687] form.reps.mentorship calls an invalid method (Can’t locate object method “realname” via package “Bugzilla::User”)
  • [1108823] removing the privacy review bug
  • [1136979] Minor Brand Initiation Form Updates
  • [880552] Add links to socorro from the crash signatures in show_bug.cgi

discuss these changes on mozilla.tools.bmo.

happy bmo push day!

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

  • [1088086] Possible duplicate search doesn’t return any results if you input “a->b” (for any a/b)
  • [1102364] Add microdata to HTML bugmail so GMail can display a “View bug” button
  • [1130721] Implement support for the attachment author for pronoun substitution in Custom Search
  • [1123275] Changes to form.reps.mentorship

discuss these changes on mozilla.tools.bmo.

happy bmo push day!

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

  • [1131622] update the description of the “Any other issue” option on the itrequest form
  • [1124810] Searching for ‘—‘ in Simple Search causes a SQL error
  • [1111343] Wrapping of table-header when sorting with “Mozilla” skin
  • [1130590] Changes to the new data compliance bug form
  • [1108816] Project kickoff form, changes to privacy review
  • [1120048] Strange formatting on inline URLs
  • [1118987] create a new bug form for discourse issues (based on form.reps.it)

discuss these changes on mozilla.tools.bmo.

happy bmo push day!

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

  • [1129291] Gear form is returning an error
  • [1128969] ‘Clone this bug’ redirects to product selection instead of displaying context menu
  • [1124255] Need a way to find only active versions and target milestones using the API
  • [1129283] “suggested reviewers” missing, due to missing YAHOO.widget.Menu
  • [1129183] 500 internal server error with duplicate mentor field
  • [1129101] Custom integer field breaks “Change many bugs at once” functionality
  • [813630] Last resolved time is displayed in server timezone not as per user preferences
  • [1129915] Promote ‘Firefox for iOS’ to the main ‘file a bug’ page
  • [1130895] Bugzilla comment tags suggestions/autocomplete isn’t working
  • [1131036] BzAPI searches no longer working
  • [1130885] change itrequest form from mozilla.org::Server Operations to Infrastructure & Operations :: MOC: Service Requests

discuss these changes on mozilla.tools.bmo.

happy bmo push day!

https://globau.wordpress.com/wp-admin/post-new.php
the following changes have been pushed to bugzilla.mozilla.org:

  • [1126315] Add rewrite rule to htaccess to properly map BzAPI requests to the BzAPI compatibility extension path
  • [1100382] support jquery in the global/header template, and update the header and footer to use jquery
  • [1127282] The bug_mentor quicksearch field is impossible to guess
  • [1059419] Needinfo-ing a mentor doesnt work
  • [1045145] All authenticated WebServices methods should require username/pass, token or a valid API key for authentication
  • [1124626] Highlight the comment that was linked
  • [1106121] Create a Bugzilla form for Firefox costume requests
  • [1123769] add a “rank” field to bugzilla to track priority
  • [1050226] Offer web devs a more focused set of product/components to file bugs in
  • [1128401] user-menu down-drop arrows are miss-aligned
  • [1088082] Can’t see non-comment changes after comment #0 until comment #1 appears if using description + newest to oldest comment sorting

discuss these changes on mozilla.tools.bmo.

Follow

Get every new post delivered to your Inbox.

Join 94 other followers