Category Archives: mozilla

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.

happy bmo push day!

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

  • [1122269] no longer have access to https://bugzilla.mozilla.org/cvs-update.log
  • [1119184] Securemail incorrectly displays ” You will have to contact bugzilla-admin@foo to reset your password.” for whines
  • [1122565] editversions.cgi should focus the version field on page load to cut down on need for mouse
  • [1124254] form.dev-engagement-event: More changes to default NEEDINFO
  • [1119988] form.dev-engagement-event: disabled accounts causes invalid/incomplete bugs to be created
  • [616197] Wrap long bug summaries in dependency graphs, to avoid horizontal scrolling
  • [1117345] Can’t choose a resolution when trying to resolve a bug (with canconfirm rights)
  • [1125320] form.dev-engagement-event: Two new questions
  • [1121594] Mozilla Recruiting Requisition Opening Process Template
  • [1124437] Backport upstream bug 1090275 to bmo/4.2 to whitelist webservice api methods
  • [1124432] Backport upstream bug 1079065 to bmo/4.2 to fix improper use of open() calls

discuss these changes on mozilla.tools.bmo.

changing the face of bugzilla.mozilla.org

background

bugzilla.mozilla.org presents some interesting problems when it comes to UX; while it has a singular view of bug data, most teams use bugzilla in slightly different ways.  some of these differences surface in fields used to track work (keywords, flags, whiteboard, summary), how bugs are prioritised (whiteboard, custom fields, priority fields), and even how inter-bug dependancies are tracked.

the net result is trying to design an user interface for viewing bugs optimised for how people use bugzilla is a near impossible task.  in light of this, we’ve been working on a framework which allows us to deploy multiple experimental alternative view of bugs.

goals

the goals are to enable alternative bug views in a way which enables rapid development and doesn’t force incomplete or broken implementations upon users.

implemented as a bugzilla extension, alternativeUI provides a harness for alternative bug views, and implements the view selection – currently as a simple user preference.  in the future we expect bugzilla to be able to automatically change view depending on the bug or your relationship to it.  for example, we could present a slightly (or radically!) different view of a bug to the assignee vs. the reviewer vs. someone not involved in the bug.

generic show_bug alternative

of course a framework for alternative bug views would be useless without an actual alternative.  i’ve been working on one which will likely be the basis of future experiments.  show/edit modality is at the core of this design — a bug is loaded with most fields as static text and switching to “edit mode” is required to make changes.

ideas we’re throwing around:

hiding fields

if a field doesn’t have a value set there’s no need for that field to be displayed by default.  removing those fields from the initial display greatly reduces the noise and complexity generally associated with bugzilla.

we can also use the user’s group membership or involvement in the bug as a cue to which data should be initially visible.  an example would be hiding the QE flags from users who are not associated with the bug or members of a the QE team.

performance

when a bug is loaded right now in bugzilla, it has to load all the alternatives for many fields (products, components, versions, milestones, flags, …).  in most cases bugzilla’s fine-grained security model results in a measurable cost to generating these alternatives — you can see the difference yourself by logging out of bugzilla or opening a bug in a private tab and comparing the page load times against a logged-in request.

by loading a bug as read-only initially, we can defer loading the alternatives until after the user clicks on ‘edit’.

selected “editable by default”

requiring a mode switch to perform any change to a bug isn’t an ideal situation either – operations that are frequently performed should be easy to do with minimal extraneous steps.

the current implementation allows you to comment, CC, or vote for a bug without switching to edit mode.  this can be extended to, for example, allow the bug’s assignee to change a bug’s status/resolution without needing to switch to edit mode.

screenshots

bmo-modal-1

bmo-modal-2

Follow

Get every new post delivered to your Inbox.

Join 93 other followers