766
edits
DaveLawrence (talk | contribs) |
DaveLawrence (talk | contribs) No edit summary |
||
| Line 67: | Line 67: | ||
== Keywords and the Whiteboard == | == Keywords and the Whiteboard == | ||
''What are all these keywords and weird whiteboard stuff? What is a whiteboard anyhow? Which should i use?'' | ''What are all these keywords and weird whiteboard stuff? What is a whiteboard anyhow? Which should i use?'' | ||
'''Keywords''' | |||
These are a limited set of keyword tags, set by teams and people with admin privilege. You can start typing a tag and get a dropdown menu of all the keywords currently available. Keywords like "regression" and "crash" are used by engineering, release, and QA teams, for example. | |||
'''Whiteboard''' | |||
The whiteboard field is for free tagging. It's used both by teams and by people who want to track bugs they're interested in. | |||
== Tracking Flags == | == Tracking Flags == | ||
''tracking-firefox-20? Who's doing the tracking? Should i even set these flags?'' | ''tracking-firefox-20? Who's doing the tracking? Should i even set these flags?'' | ||
= Needinfo Flag = | Tracking flags are used by developers, triagers, QA and the release management teams to keep track of bugs whose fixes are slated to go into a particular product release. Flags of the form tracking-firefox-26 have a ?, +, or - associated. | ||
For example, a [https://bugzilla.mozilla.org/buglist.cgi?f1=cf_tracking_firefox26&list_id=7974674&o1=substring&resolution=---&resolution=DUPLICATE&query_format=advanced&v1=%2B search for tracking-firefox-26 and "+"] currently shows around 50 bugs. | |||
If you would like to suggest a bug and its fix be considered (by release managers) for a particular release, mark it with that release and a question mark. This might be good to do for a bug that's been fixed in one release channel but needs to be uplifted to another. | |||
[[Release_Management/Release_Process#All_about_Flags|More information on Firefox Flags]] | |||
== Needinfo Flag == | |||
''It's good and you should use it.'' | ''It's good and you should use it.'' | ||
If you have a question about a bug, and you'd like to direct that question to a specific person, you can do that easily with the needinfo flag. | |||
The person you need info from will get bugmail with (look up the X-Bugzilla-header) in the header. This may get a person's attention faster than adding them to the CC list of a bug. | |||
You can see the needinfo flags you have requested of others and the ones requested of you in your [https://bugzilla.mozilla.org/page.cgi?id=mydashboard.html Dashboard]. | |||
= Other Ways to use BMO and its Data = | = Other Ways to use BMO and its Data = | ||
| Line 78: | Line 98: | ||
== Whining == | == Whining == | ||
''Bugzilla can automatically send you buglists (requires canconfirm).'' | ''Bugzilla can automatically send you buglists (requires canconfirm).'' | ||
BMO can automatically send you buglists (or a group of people) at defined intervals. This requires that you have specific rights required to [https://bugzilla.mozilla.org/editwhines.cgi create whines]. | |||
== APIs == | == APIs == | ||
''I hear you want to integrate with BMO. Where to start, what to do next, and best practices which won't get you blocked.'' | ''I hear you want to integrate with BMO. Where to start, what to do next, and best practices which won't get you blocked.'' | ||
BMO has a REST API that can perform most common tasks and is great for allowing external systems to integrate with Bugzilla. More details on how to use the API can be found [http://bmo.readthedocs.io/en/latest/api/index.html here]. | |||
== Dashboards == | == Dashboards == | ||
''Trying to answer the "what should i do today" question? Go no further than the dashboards.'' | ''Trying to answer the "what should i do today" question? Go no further than the dashboards.'' | ||
[https://bugzilla.mozilla.org/page.cgi?id=mydashboard.html My Dashboard] has some nice options for viewing lists of bugs that may be of interest to you. | |||
[https://bugzilla.mozilla.org/page.cgi?id=productdashboard.html Product Dashboard] has many ways to look at data about bugs associated with particular products and components. The reports are listed in tabs: Summary, Recents, Components/Versions, Duplicates, Roadmap, and Popularity. They're all worth exploring. | |||
[[Category:BMO]] | [[Category:BMO]] | ||
edits