Defect Status and Resolution Relationship Explained

 

STATUS	RESOLUTION
The status field indicates the general health of a bug. Only certain status transitions are allowed.	The resolution field indicates what happened to this bug.
UNCONFIRMED NEW ASSIGNED REOPENED	No Resolution when bug status is new, assigned and reopened.
RESOLVED	FIXED INVALID WONTFIX DUPLICATE WORKSFORME MOVED
VERIFIED	FIXED INVALID WONTFIX DUPLICATE WORKSFORME MOVED
CLOSED	FIXED INVALID WONTFIX DUPLICATE WORKSFORME MOVED

New, Assigned, Reopened: When bug status is “New”, “Assigned” and “Reopened” there is no resolution. Bug can be assigned to developer to fix the bug. When bug is “New” it is assigned to an email id called DevTeam@neuron.com. When assigned to DevTeam@neuron.com, it is a group email and is sent to all the development team. (or it can even be sent only to development lead in some organization)

Assigned: Bug status is changed from New to Assigned, when Development lead will assign the bug to developer. Email id will be changed from DevTeam@nuron.com to Mike.Welch@neuron.com. (Considering Mike as one of the neuron developer) (In some organization, developer will assign the bug to themselves, instead of waiting for development lead to assign it to them)

Resolved: Bug status is “Resolved”, it’s resolution should be marked as fixed, invalid, worksForMe etc. by developer. Bug is sometimes assigned to tester. Assigned here means, only email id is changed from Mike.Welch@neuron.com to TestTeam@neuron.com. (In many organization bug is not assigned to tester, testers should pick up by searching all the resolved fixed bugs. Most of the bug tracking tools sends email to bug reporter when the bug status is changed.

When bug is marked as resolved: fixed, invalid, wontfix, duplicate etc. testers picks the bug:

• If the bug is marked as resolved: fixed, tester will Verify the bug and mark the bug as verified fixed
• If the bug is marked as resolved: invalid, wontfix, duplicate, worksforme etc, Tester have to make sure if bug is reproducible in recent version or bug can be reproduced in test environment. Even when bug marked as duplicate, tester have to make sure, if bug is really a duplicate of another bug
• If the bug is reproducible in Test Environment, bug should be reopened
• If the bug is reopened, developer lead will again assign the bug to developer and developer can ask the tester to reproduce the bug in test environment in front of him or ask for exact steps and environment to reproduce.
• It is important to have detail bug report with steps to reproduce, screen shot of error, test environment details, product version number etc.

Bug is marked as Closed by Test Manager when Bug is left as Resolved: resolved: invalid, wontfix, duplicate, worksforme etc or Verified: resolved: invalid, wontfix, duplicate, worksforme etc.