MozillaWiki

Firefox/searchandaddon: Difference between revisions

Page Discussion

Firefox/searchandaddon (view source)

Revision as of 18:52, 17 May 2016

2,976 bytes added ,  17 May 2016
m
→‎Key Bugzilla Queries: fixed query
 
(19 intermediate revisions by the same user not shown)
Line 17: Line 17:


==Key Bugzilla Queries==
==Key Bugzilla Queries==
* '''Team Product Backlog:'''  [http://mzl.la/1EjFTk8 Bugs marked Firefox-backlog+ and [fxsearch]]
* '''[http://mzl.la/1TGrUtG Team Product Backlog]:''' 
**Add the "Rank" Column to your results and sort on Rank (option to "Change columns" is at bottom of search results)
** Add '''fxsearch''' to triaged bugs and set Priority
*'''Bugs Pulled Current Iteration:'''[http://tinyurl.com/lxfd4xp Bugs in the Backlog with a current iteration tag]
**Optional
**for  Assignee: dtownsend@mozilla.com, dao@mozilla.com, mak77@bonardo.net, mjaritz@mozilla.com, shorlander@mozilla.com, adw@mozilla.com, markh@mozilla.com, florian@queze.net
***Add a '''short descriptive area tag''' in the whiteboard when possible, to visually group bugs quickly in a list. ex: "[visual refresh] fxsearch"
*'''Untriaged Bugs marked Firefox-backlog+:''' [http://tinyurl.com/nnlffev Bugs marked Firefox-backlog+ without [fxsearch]] in the Whiteboard under Search
**'''Importance''' will be left at default, "normal", unless a bug is on the line of being one Priority higher and lower - and then will be marked "Major" or "Minor" accordingly.
*'''[http://mzl.la/1Jro4Tx Untriaged bugs marked [fxsearch]]''' without Firefox-backlog+
* '''Priorities''' follow this Standard:
*'''Untriaged Bugs:'''[http://tinyurl.com/naufrjz Bugs NOT marked Firefox-backlog+ without [fxsearch]] in whiteboard under Search
** Priority 1 - Blocker, must-fix before shipping or a priority feature we are including in this release.
** Priority 2 - Major impact, considering severity × probability. Not a blocker for shipping. For Features we'd really like it, but wouldn't hold shipping for it.
** Priority 3 - Average Bug. definitely a problem, but doesn't stop someone from using the product.  
** Priority 4 - Minor or polish bugs that are real issues (especially in aggregate) and annoying.
** Priority 5 - Low-impact. something we'd fix, but mostly only bothers the discerning user. Little impact on usability.
<p> </p>
 
<p> </p>
*'''[http://mzl.la/1LqCwiy Untriaged Bugs]:'''Bugs under Firefox::Search without [fxsearch] in whiteboard
<p> </p>
<p> </p>


Line 40: Line 48:
* '''Iteration 42.3:'''  Tuesday July 28 - Monday August 10
* '''Iteration 42.3:'''  Tuesday July 28 - Monday August 10
<p> </p>
<p> </p>
==Themes==
==Themes==
As we plan what's coming next, [https://docs.google.com/a/mozilla.com/document/d/1de2o8Osl_z98BBfkt243i-dHdcKmQB15xJ9rShkwk3Q/edit?usp=sharing these are areas being discussed].  This is not a commitment to the next projects - just our scratch area, but it is in order of relative priority - including the work we've pulled for the sprints.
As we plan what's coming next, [https://docs.google.com/a/mozilla.com/document/d/1de2o8Osl_z98BBfkt243i-dHdcKmQB15xJ9rShkwk3Q/edit?usp=sharing these are areas being discussed].  This is not a commitment to the next projects - just our scratch area, but it is in order of relative priority - including the work we've pulled for the sprints.
*'''Unified Autocomplete:''' Necessary maintenance work to make the awesomebar easier to improve
*'''Partner Engine:''' issues relating to the integration of our partner's search engines
*'''Search Suggestions:''' Adding search suggestions to the awesomebar
*'''Search Suggestions:''' Adding search suggestions to the awesomebar
*'''Search Hijacking:''' Keep users on the search engine that they want
*'''Search Hijacking:''' Keep users on the search engine that they want
**'''Add-on Signing'''  
**'''Add-on Signing'''  
*'''Search UI:''' basically how our search access points work/look
*'''Search UI:''' basically how our search access points work/look
*'''Partner Engine:''' issues relating to the integration of our partner's search engines
 
<p></p>
<p></p>
Things we want to do - but not starting until higher priorities are done:
Things we want to do - but not starting until higher priorities are done:
Line 64: Line 72:


==Current==
==Current==
===Iteration - 41.3, through June 29===
[https://bugzilla.mozilla.org/show_bug.cgi?id=958204 Theme 958204] '''Search Suggestions'''
<p> </p>
{| class="wikitable collapsible collapsed" style="width: 100%"
! Suggestions: Allow user to select a query from search suggestions in Awesome Bar
|-
|
* '''ID:'''  [https://bugzilla.mozilla.org/show_bug.cgi?id=1162140 Bug 1162140]
** Suggestions was turned on in Nightly to find bugs
** Disabled now until we land "opt-in/opt-out" user choice control.
<p> </p>
<bugzilla>
{
"f1":"blocked",
"o1":"equals",
"v1":"1162140",
"include_fields":"id, summary, status, assigned_to, cf_fx_points"
}
</bugzilla>
|}
<p> </p>
<p> </p>
{| class="wikitable collapsible collapsed" style="width: 100%"
! Suggestions: Search Suggestions in the AwesomeBar should be clearly identified as such
|-
|
* '''ID:'''  [https://bugzilla.mozilla.org/show_bug.cgi?id=1162142 Bug 1162142]
* UX done - hoping work will be done as well - dependent on bugs from landing first part of search and auto complete bugs
<p> </p>
<bugzilla>
{
"f1":"blocked",
"o1":"equals",
"v1":"1162142",
"include_fields":"id, summary, status, assigned_to, cf_fx_points"
}
</bugzilla>
|}
<p> </p>
{| class="wikitable collapsible collapsed" style="width: 100%"
! Partner Engine: Support server-driven setting of search defaults
|-
|
* '''ID:'''  [https://bugzilla.mozilla.org/show_bug.cgi?id=1169280 Bug 1169280]
* Asked for status on server side work - checking on other potentially required bugs.
<p> </p>
<bugzilla>
{
"f1":"blocked",
"o1":"equals",
"v1":"1169280",
"include_fields":"id, summary, status, assigned_to, cf_fx_points"
}
</bugzilla>
|}
<p> </p>
'''Details'''
* Biz dev project has taken priority.  Florian is 100% devoted to that work
* UX design for opt-in/opt-out is a priority (as Search Suggestions is disabled until this lands)
** [https://bugzilla.mozilla.org/show_bug.cgi?id=1169280 Bug 959567[User Story] Implement search suggestions opt-in/out UI] is candidate for Aurora uplift if we don't get implemented in 41.3
*'''Unified Autocomplete''' bugs are being resolved (large project / several bugs)
**Will enable in Nightly in this iteration
<p> </p>
Collection of priority work the team has committed to complete on in a two-week iteration.
<p> </p>
*[https://wiki.mozilla.org/Firefox/searchandaddon#Key_Bugzilla_Queries view in Bugzilla]
<p> </p>
<bugzilla>
{
        "assigned_to": "dtownsend@mozilla.com, dao@mozilla.com, mak77@bonardo.net, mjaritz@mozilla.com, shorlander@mozilla.com, adw@mozilla.com, markh@mozilla.com, florian@queze.net",
        "include_fields":"id, summary, status, assigned_to, whiteboard, cf_fx_points",
        "cf_fx_iteration":"41.3 - Jun 29"
}
</bugzilla>
<p> </p>
<p> </p>
==Past==
===Iteration - 41.2, through June 8===
===Iteration - 41.2, through June 8===
User Story this iteration: "As a user, when I enter text in the location bar, I will be presented with suggested search queries from the search default in the AwesomeBar dropdown that update as I continue to enter text to provide me with common queries related to the text I have entered."
User Story this iteration: "As a user, when I enter text in the location bar, I will be presented with suggested search queries from the search default in the AwesomeBar dropdown that update as I continue to enter text to provide me with common queries related to the text I have entered."
Line 91: Line 190:


<p> </p>
<p> </p>
==Past==


===Iteration - 41.1, through May 25===
===Iteration - 41.1, through May 25===
Sescalante
Confirmed users
1,094

edits

Retrieved from "https://wiki.allizom.org/Special:MobileDiff/1078354...1133043"