BMO/User profile fields: Difference between revisions
< BMO
Jump to navigation
Jump to search
(Created page with "These are descriptions of the fields listed on the user profile pages in bugzilla.mozilla.org. '''Last activity''' The date and time a user last reported, changed or commen...") |
(Tentative page as the existing is not found.) |
||
| (4 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
These are descriptions of the fields listed on the user profile pages | These are descriptions of the fields listed on the user profile pages on bugzilla.mozilla.org. | ||
=== Last activity === | |||
The date and time a user last reported, changed or commented on a bug in | The date and time a user last reported, changed or commented on a bug in Bugzilla. Link to user activity report for the last 4 weeks. | ||
=== Bugs filed === | |||
The total number of bugs reported by the user. | The total number of bugs reported by the user. | ||
* [[How to File a Bug]] | |||
=== Commented on === | |||
The total number of bugs that the user has commented on. | The total number of bugs that the user has commented on. | ||
=== Comments made === | |||
The total number of comments that the user has added. | The total number of comments that the user has added. | ||
=== Confirmed === | |||
The number of bugs the user has changed from UNCONFIRMED to NEW. | The number of bugs the user has changed from UNCONFIRMED to NEW. | ||
* [https://developer.mozilla.org/en-US/docs/Mozilla/QA/Confirming%5Funconfirmed%5Fbugs Confirming UnconfirmedBugs] | |||
=== QA-contact === | |||
QA-contacts work as part of the QA team to help developers with regression testing, steps to reproduce bugs, and bug verification. | QA-contacts work as part of the QA team to help developers with regression testing, steps to reproduce bugs, and bug verification. | ||
* [https://developer.mozilla.org/en-US/docs/Mozilla/QA/How_can_I_help_test_/ How Can I Help Test?] | |||
=== Patches submitted === | |||
The number of patches a user has submitted to help fix a bug. | The number of patches a user has submitted to help fix a bug. | ||
* [https://developer.mozilla.org/en-US/docs/Introduction Contributing to the Mozilla Codebase] | |||
* [https://developer.mozilla.org/en-US/docs/Developer%5FGuide/How%5Fto%5fSubmit%5fa%5fPatch How to Submit a Patch] | |||
* [[Bugzilla:Review|Bugzilla:Review]] | |||
=== Patches reviewed === | |||
Shows how many patches a user has reviewed. | Shows how many patches a user has reviewed. | ||
* [https://developer.mozilla.org/en-US/docs/Code%5FReview_FAQ Code Review FAQ] including how to become a reviewer | |||
=== Assigned to === | |||
Bugs assigned to a user. | Bugs assigned to a user. | ||
=== Bugs poked === | |||
Total number of bugs a user has interacted with: filed, commented on, changed status, added whiteboard or keyword tags, changed product or component; anything done to the bug that results in saving changes. | Total number of bugs a user has interacted with: filed, commented on, changed status, added whiteboard or keyword tags, changed product or component; anything done to the bug that results in saving changes. | ||
=== RESOLVED === | |||
Bugs a user has changed from NEW, UNCONFIRMED, or REOPENED to RESOLVED. | Bugs a user has changed from NEW, UNCONFIRMED, or REOPENED to RESOLVED. | ||
* [https://developer.mozilla.org/en-US/docs/What%5Fto%5Fdo%5Fand%5Fwhat%5Fnot%5Fto%5Fdo%5Fin%5FBugzilla#Resolving_bugs Resolving bugs] | |||
=== DUPLICATE === | |||
Bugs a user has resolved as a duplicate of an existing bug | Bugs a user has resolved as a duplicate of an existing bug. | ||
* [https://developer.mozilla.org/en-US/docs/Screening%5Fduplicate%5Fbugs Screening DUPLICATE bugs] | |||
=== INVALID === | |||
Bugs a user has resolved as INVALID; these may be issues that aren't Mozilla bugs, or are features rather than unexpected behavior. | Bugs a user has resolved as INVALID; these may be issues that aren't Mozilla bugs, or are features rather than unexpected behavior. | ||
* [https://developer.mozilla.org/en-US/docs/What%5Fto%5Fdo%5Fand%5Fwhat%5Fnot%5Fto%5Fdo%5Fin%5FBugzilla#Resolving_bugs Resolving bugs as INVALID] | |||
=== WORKSFORME === | |||
Bugs a user was unable to reproduce on the reported hardware and OS. | Bugs a user was unable to reproduce on the reported hardware and OS. This includes bugs which used to be reproducible, but have "spontaneously disappeared", without it being known exactly what fixed the bug. | ||
* [https://developer.mozilla.org/en-US/docs/What%5Fto%5Fdo%5Fand%5Fwhat%5Fnot%5Fto%5Fdo%5Fin%5FBugzilla#Resolving_bugs Resolving bugs] | |||
=== FIXED === | |||
Bugs a user has resolved as FIXED. Only verify FIXED if the bug's resolution can be tied to a specific code checkin in a Mozilla repository. | Bugs a user has resolved as FIXED. Only verify FIXED if the bug's resolution can be tied to a specific code checkin in a Mozilla repository. | ||
* [https://developer.mozilla.org/en-US/docs/What%5Fto%5Fdo%5Fand%5Fwhat%5Fnot%5Fto%5Fdo%5Fin%5FBugzilla#Resolving_bugs Resolving bugs as FIXED] | |||
=== VERIFIED === | |||
Resolved bugs that a user has made sure have been resolved correctly. | Resolved bugs that a user has made sure have been resolved correctly. | ||
* [https://developer.mozilla.org/en-US/docs/What%5Fto%5Fdo%5Fand%5Fwhat%5Fnot%5Fto%5Fdo%5Fin%5FBugzilla#Verifying_bugs Verifying bugs] | |||
==Activity by product== | |||
Currently this gathers actions performed on bugs rather than counting the number of bugs. So the numbers here will be larger than the total number of bugs a user has worked on. We may change this in future if it seems confusing. The point would be to reflect the products where a user most often focuses their work. | |||
Latest revision as of 16:25, 4 August 2015
These are descriptions of the fields listed on the user profile pages on bugzilla.mozilla.org.
Last activity
The date and time a user last reported, changed or commented on a bug in Bugzilla. Link to user activity report for the last 4 weeks.
Bugs filed
The total number of bugs reported by the user.
Commented on
The total number of bugs that the user has commented on.
Comments made
The total number of comments that the user has added.
Confirmed
The number of bugs the user has changed from UNCONFIRMED to NEW.
QA-contact
QA-contacts work as part of the QA team to help developers with regression testing, steps to reproduce bugs, and bug verification.
Patches submitted
The number of patches a user has submitted to help fix a bug.
Patches reviewed
Shows how many patches a user has reviewed.
- Code Review FAQ including how to become a reviewer
Assigned to
Bugs assigned to a user.
Bugs poked
Total number of bugs a user has interacted with: filed, commented on, changed status, added whiteboard or keyword tags, changed product or component; anything done to the bug that results in saving changes.
RESOLVED
Bugs a user has changed from NEW, UNCONFIRMED, or REOPENED to RESOLVED.
DUPLICATE
Bugs a user has resolved as a duplicate of an existing bug.
INVALID
Bugs a user has resolved as INVALID; these may be issues that aren't Mozilla bugs, or are features rather than unexpected behavior.
WORKSFORME
Bugs a user was unable to reproduce on the reported hardware and OS. This includes bugs which used to be reproducible, but have "spontaneously disappeared", without it being known exactly what fixed the bug.
FIXED
Bugs a user has resolved as FIXED. Only verify FIXED if the bug's resolution can be tied to a specific code checkin in a Mozilla repository.
VERIFIED
Resolved bugs that a user has made sure have been resolved correctly.
Activity by product
Currently this gathers actions performed on bugs rather than counting the number of bugs. So the numbers here will be larger than the total number of bugs a user has worked on. We may change this in future if it seems confusing. The point would be to reflect the products where a user most often focuses their work.