BMO/User profile fields

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.

• How to File a Bug

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.

• 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.

• How Can I Help Test?

Patches submitted

The number of patches a user has submitted to help fix a bug.

• Contributing to the Mozilla Codebase
• How to Submit a Patch
• Bugzilla:Review

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.

• Resolving bugs

DUPLICATE

Bugs a user has resolved as a duplicate of an existing bug.

• 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.

• Resolving bugs as INVALID

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.

• 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.

• Resolving bugs as FIXED

VERIFIED

Resolved bugs that a user has made sure have been resolved correctly.

• 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.