Bugzilla: Difference between revisions Discussion View history

No edit summary
(Heading corrections and Status Workflow formatting)
Line 3: Line 3:
[https://bugs.waze.com/ Waze Bugzilla] is partially open to the community with different access level permissions in order to make the status of bugs and feature requests visible.
[https://bugs.waze.com/ Waze Bugzilla] is partially open to the community with different access level permissions in order to make the status of bugs and feature requests visible.


=Structure=
== Structure ==


We have two '''classifications''' in which the items are organized:
There are two '''classifications''' in which the items are organized:


# '''''Internal''''' - accessible to Waze staff only
# '''''Internal''''' - accessible to Waze staff only
# '''''Public''''' - accessible to all with different permission levels
# '''''Public''''' - accessible to all with different permission levels


Most items will be in the public area, but some will be restricted and visible to staff only. We'd usually want to be transparent, but sometimes we are limited by privacy and security concerns.
Most items will be in the public area, but some will be restricted and visible to staff only. This is sometimes necessary due to privacy and security concerns.


Each classification contains two '''products''' - the general Waze client and services product, and the Waze Map Editor product.
Each classification contains two '''products''' - the general Waze client and services, and the Waze Map Editor.


=Permissions=
== Permissions ==


==View only==
=== View only ===


Anyone can access and see all of the public bugs with no need to login. Internally, we can mark some of the comments as private for staff only, but the rest of the details are publicly visible.
Anyone can access and see all of the public bugs with no need to login. Internally, some of the comments are marked private for staff only, but the rest of the details are publicly visible.


==Comment & Vote==
=== Comment & Vote ===


This permission level requires a login.
This permission level requires a login which is obtained by submitting an [https://docs.google.com/a/waze.com/forms/d/1N_fTFguhWRYdwSgmdODaPSMV7-hYH0YsaGmEyTpPfuI/viewform application] which will be reviewed by Waze staff.
A login requires submitting an [https://docs.google.com/a/waze.com/forms/d/1N_fTFguhWRYdwSgmdODaPSMV7-hYH0YsaGmEyTpPfuI/viewform application].
*At this time, only the following will be eligible for a login:
*At this time, only the following will be eligible for a login:
**Local / Global champs
**Local / Global champs
**Experts / Coordinators
**Experts / Coordinators
**Editor/App beta-testers
**Editor / App beta-testers


The users in this permission level have the right to vote on 25 items they think are the most critical, and to add comments with additional information about bugs and features.  
The users in this permission level have the right to vote on 25 items they think are the most critical, and to add comments with additional information about bugs and features.


==Bug Submitters==
=== Bug Submitters ===
Bug Submitters have permission to post [[Bugzilla how to guide | new bugs]] and are hand-picked by Waze.
Bug Submitters have permission to post [[Bugzilla how to guide | new bugs]] and are hand-picked by the Waze staff.


=General guidelines=
== General guidelines ==
===Voting===
=== Voting ===
*Vote on what you think are the most pressing issues we need to address. Votes are your method to express your concerns. We deeply care about the concerns of our community, we consider the vote count, and try to prioritize our development process according to it. There are other things we are forced to consider such as development dependencies, infrastructure issues, business development, things that are easier / harder to develop, etc. However - your votes are your voice and it's important to us. Use them wisely.
*For those who can vote, please focus on the most pressing issues that need to be addressed. This is going to be the best method to express community concerns. The Waze team will consider the vote count and try to prioritize the overall development to take this into consideration. While there are other items to consider in allocating development resources (business needs, infrastructure issues, other dependencies), the votes are important to the Waze team.  


===Commenting===
=== Commenting ===


If you have the appropriate permission level, you are welcome to provide more information using the commenting system.
If you have the appropriate permission level, you are welcome to provide more information using the commenting system.
Line 45: Line 44:
*Requirements - specific use cases which are difficult to perform with the current implementation.
*Requirements - specific use cases which are difficult to perform with the current implementation.


We are trying to keep everything very focused. Try to refrain from adding irrelevant information such as off-topic discussion, reproduction of other issues, requests, opinions, social interaction, etc - this things are what the forums are for.
Please refrain from adding irrelevant information such as off-topic discussion, reproduction of other issues, requests, opinions, social interaction, etc. These things should be discussed in the forums.


===Duplicates===
=== Duplicates ===


One thing one should be careful when managing an issue tracking system is duplicate entries. Before asking our experts to open a new bug report, please verify that it hasn't been already reported using the search tools.
Before asking the Waze experts to open a new bug report, please verify that it hasn't been already reported using the [[Bugzilla_how_to_guide#Searching|Bugzilla search tools]].


=Public Products=
== Public Products ==
 
The following products are covered in the Waze Bugzilla:
*[[Waze Version 3.5 | The Waze application]]
*[[Waze Version 3.5 | The Waze application]]
*[[Waze Map Editor | The Waze Map Editor]]
*[[Waze Map Editor | The Waze Map Editor]]


=Map Editor Bugzilla=
== Map Editor Bugzilla ==


These guidelines are specific to the map editor product.
These guidelines are specific to the map editor product.


===Issue types===
=== Issue types ===


The '''Issue Type''' field says whether an issue is Bug or Requirement. Bug means something that should already work but is not working correctly, a requirement means a feature we'd like to see implemented.
The '''Issue Type''' field says whether an issue is Bug or Requirement. Bug means something that should already work but is not working correctly, a requirement means a feature we'd like to see implemented.


===Prioirty ratings===
=== Priority ratings ===
 
'''Priority Rating''' is the ranking Waze uses to prioritize what issues get attention first. The scale is 1-1000 with 1000 meaning "we're-not-going-to-sleep-until-it's-done," and 1 is maybe-someday. The priority is set according to all the considerations Waze must take into account for the development team, and may change the priority as other conditions change.


'''Priority Rating''' is the ranking we set for the issue. The scale is 1-1000, 1000 is we're-not-going-to-sleep-until-it's-done, 1 is maybe-someday. We set the prioirty according to all the considerations we take into account, and may change it when the conditions change.
=== Status Workflow ===


===Status Workflow===
The Waze team will change the status from one setting to another depending on the following conditions:


We change status from '''UNCONFIRMED''' to '''CONFIRMED''' or another status as soon as we go over an issue to make sure we understand what it means. Sometimes we will change the status to '''NEED INFO''' which means, uhm, that we need more info - usually specific steps to reproduce a bug. '''IN PROGRESS''' means we are currently working on this. '''RESOLVED''' means we fixed the bug and deployed it to the beta environment, '''VERIFIED''' means it does not reoccur after deployment.
* '''UNCONFIRMED''' - All initial reports start with this status. It stays here until the Waze team does an initial review of the report.
* '''CONFIRMED''' - The report is understood and/or can be reproduced.
* '''NEED INFO''' - The Waze team was unable to reproduce the report with the information provided.
* '''IN PROGRESS''' - The report is currently being worked.
* '''RESOLVED''' - The issue has been fixed or developed and should be deployed in the beta environment shortly
* '''VERIFIED''' - Problems reports no longer reoccur after deployment and new features are working as designed.


===Build number===
=== Build number ===


When submitting a bug, it is important to note what was the active editor sub-version the bug was identified in. In the beta editor you can see the currently deployed version in the top left corner. v1.2-32 means version 1.2, and the build number is 32.
When submitting a bug, it is important to note what was the active editor sub-version the bug was identified in. In the beta editor you can see the currently deployed version in the top left corner. v1.2-32 means version 1.2, and the build number is 32.

Revision as of 16:32, 17 June 2013

Bugzilla is an external issue tracking system used internally by Waze technical teams.

Waze Bugzilla is partially open to the community with different access level permissions in order to make the status of bugs and feature requests visible.

Structure

There are two classifications in which the items are organized:

  1. Internal - accessible to Waze staff only
  2. Public - accessible to all with different permission levels

Most items will be in the public area, but some will be restricted and visible to staff only. This is sometimes necessary due to privacy and security concerns.

Each classification contains two products - the general Waze client and services, and the Waze Map Editor.

Permissions

View only

Anyone can access and see all of the public bugs with no need to login. Internally, some of the comments are marked private for staff only, but the rest of the details are publicly visible.

Comment & Vote

This permission level requires a login which is obtained by submitting an application which will be reviewed by Waze staff.

  • At this time, only the following will be eligible for a login:
    • Local / Global champs
    • Experts / Coordinators
    • Editor / App beta-testers

The users in this permission level have the right to vote on 25 items they think are the most critical, and to add comments with additional information about bugs and features.

Bug Submitters

Bug Submitters have permission to post new bugs and are hand-picked by the Waze staff.

General guidelines

Voting

  • For those who can vote, please focus on the most pressing issues that need to be addressed. This is going to be the best method to express community concerns. The Waze team will consider the vote count and try to prioritize the overall development to take this into consideration. While there are other items to consider in allocating development resources (business needs, infrastructure issues, other dependencies), the votes are important to the Waze team.

Commenting

If you have the appropriate permission level, you are welcome to provide more information using the commenting system.

  • Bugs - ways to reproduce them, description of environments in which they occur, examples.
  • Requirements - specific use cases which are difficult to perform with the current implementation.

Please refrain from adding irrelevant information such as off-topic discussion, reproduction of other issues, requests, opinions, social interaction, etc. These things should be discussed in the forums.

Duplicates

Before asking the Waze experts to open a new bug report, please verify that it hasn't been already reported using the Bugzilla search tools.

Public Products

The following products are covered in the Waze Bugzilla:

Map Editor Bugzilla

These guidelines are specific to the map editor product.

Issue types

The Issue Type field says whether an issue is Bug or Requirement. Bug means something that should already work but is not working correctly, a requirement means a feature we'd like to see implemented.

Priority ratings

Priority Rating is the ranking Waze uses to prioritize what issues get attention first. The scale is 1-1000 with 1000 meaning "we're-not-going-to-sleep-until-it's-done," and 1 is maybe-someday. The priority is set according to all the considerations Waze must take into account for the development team, and may change the priority as other conditions change.

Status Workflow

The Waze team will change the status from one setting to another depending on the following conditions:

  • UNCONFIRMED - All initial reports start with this status. It stays here until the Waze team does an initial review of the report.
  • CONFIRMED - The report is understood and/or can be reproduced.
  • NEED INFO - The Waze team was unable to reproduce the report with the information provided.
  • IN PROGRESS - The report is currently being worked.
  • RESOLVED - The issue has been fixed or developed and should be deployed in the beta environment shortly
  • VERIFIED - Problems reports no longer reoccur after deployment and new features are working as designed.

Build number

When submitting a bug, it is important to note what was the active editor sub-version the bug was identified in. In the beta editor you can see the currently deployed version in the top left corner. v1.2-32 means version 1.2, and the build number is 32.