Closed Bug 926272 Opened 7 years ago Closed 7 years ago

searching for an unset tracking flag fails since BMO upgrade on 2013-10-12

Categories

(bugzilla.mozilla.org :: Extensions, defect)

Production
defect
Not set
critical

Tracking

()

RESOLVED FIXED

People

(Reporter: jsmith, Assigned: glob)

Details

Post the BMO upgrade on 10/12/2013, I noticed some of my saved searches are no longer returning any bugs on the query. Example queries that are failing:

- Titled - B2G Non-Nominated Regressions
** Looks for keywords = regression, Product = Boot2Gecko, Resolution = ---, blocking-b2g = ---

- Titled: B2G QA Triage - Low Priority
** Looks for Product = Boot2Gecko, blocking-b2g = ---, keywords = qawanted or steps-wanted or regressionwindow-wanted or testcase-wanted, status-b2g18 = ?, status-b2g18-v1.0.1 = ?
Keywords: dataloss
prior to the migration, unset fields had a value of '---' in the bugs table, now they simply don't have an entry in a different table.

we need to convert searches for '---' to 'isempty'; working on a fix now.
Summary: Many saved searches are broken post BMO upgrade on 10/12/2013 → searching for an unset tracking flag fails since BMO upgrade on 10/12/2013
Committing to: bzr+ssh://bjones%40mozilla.com@bzr.mozilla.org/bmo/4.2/
modified Bugzilla/Search.pm
modified extensions/TrackingFlags/Extension.pm
Committed revision 9062.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Summary: searching for an unset tracking flag fails since BMO upgrade on 10/12/2013 → searching for an unset tracking flag fails since BMO upgrade on 2013-10-12
this has been pushed to production; the queries appear to be returning valid results now.
Component: Extensions: TrackingFlags → Extensions
You need to log in before you can comment on or make changes to this bug.