About Defects

You can create a defect from scratch, or from an existing Issue. The Issue must be in the Create, Assign, Active, or Review state. If the Issue is closed, you cannot raise a defect against it.

Issues are used as an external method for reporting problems in model versions or parts. "External" could be a customer, development partner, or supplier, or depending on your organization's structure, someone from another division. If the people who evaluate the Issue decide that the problem is an actual defect (and not a user error or a suggestion for a new feature), they can create a defect to resolve the problem based on that Issue. The defect then shows up on the Issue's Resolved By page.

When you create a defect from an Issue, Defect Management copies these details from the Issue to the defect:

• Description
• Reported against. If the reported against object is a model version, then it is copied to the defect. Otherwise, it is not copied.
• Steps to reproduce
• Reporting organization

Defect Engineers can view, edit, and be assigned tasks for a defect or defect action. Defect Engineers can be assigned as an Action Assignee or Quality Assignee for a defect or defect action.

Defect Managers review defects and either assign them to be fixed or reject them.

When you subscribe to a defect, you can choose the Modified event. This subscription notifies you when changes are made to the defect, and attached defect actions. Changes include new defect actions, additional notes, and any changes to attributes. You also receive notifications if someone changes items associated with the defect or defect action, such as the Environment or the Reported Against Model Version.

Action Assignees and Quality Assignees automatically receive notifications of changes to the defect, defect action, or related item.

The notification lists all the changes to an object and changes to its related objects. For example, the notification could include information about a new defect action, changes to the steps to reproduce for the defect, and notes added to the defect. The notification includes the related items that you have access to. For example, if you have access to the defect but not the defect action, you only receive notifications for the defect.

The notifications in text format first list the affected object, and then the events for that item.

Type: Defect  Name: DFT-0000001  Revision: -
2/7/2014 7:59:31  Defect Manager  modify  Submit  Branch To: was None : now Evaluate
2/7/2014 7:59:32  Defect Manager  promote  Evaluate
2/7/2014 7:59:32  Defect Manager  modify  Evaluate  Branch To: was Evaluate : now 
==========

In the above example, Defect Manager would be the actual user names who performed those actions. The notifications in HTML format show a separate table for each object. The line showing the object name is a link that you can click to open the default page for that object in a browser window.

Type: Defect Name: DFT-0000001 Revision: -