Report a defect in Agile Development 2.0
Track issues associated to your product or feature by reporting defects in Agile Development 2.0.
Before you begin
Role required: feature_user, scrum_story_creator, or scrum_admin
The administrator must grant the feature_user role to all those users who are expected to report defects using the Agile Development 2.0 application.
About this task
Create a defect record using the Defects module. You can later create a story for this defect so that the relevant assignment group can work on resolving the issues.
Procedure
Navigate to All > Agile Development > Defects.
Select New.
On the form, fill in the fields.
| Field | Description |
|---|---|
| Number | System-generated unique identifier for the defect. |
| Priority | Priority assigned to the defect. A product owner can use priorities when creating stories. |
| State | State of the defect. Select one of the following:- Draft:The defect details are still being drafted. - Scoping: The defect is being triaged and the scope of the defect and its fix is being analyzed. - Awaiting approval: The scope of the defect is finalized and the team is awaiting approval to start working on it. - Work in progress: The team is working on the fix for the defect. - Testing/QA: The tester is testing the defect fix based on the scope provided. - Deploy/Launch: The team is ready to launch the fix for the defect. - Closed Complete: The fix for the defect is deployed into the product. - On Hold: The defect is put on hold due to any blockers and until further review. - Cancelled: The team cancels working on this defect. This field is automatically set to Draft. |
| Assignment group | The group to which the defect belongs. |
| Assigned to | The user assigned to the defect. |
| Product | Product with which this defect is associated. The field is required if the defect is part of a product. |
| Reported against | Problem, change, or other task record that this defect is reported against. |
| Short Description | Brief description of the defect. |
| Description | Detailed description of the defect. |
| Work notes | Notes about the work being performed on the defect. Work notes can be updated as the work progresses on this defect. |
- Select Submit.
Result
The defect is created and the form reopens with the Stories related list. The list of stories is only visible to users with a scrum role.
What to do next
A scrum product owner can review the defect and decide if a story must be created for it. See Create a story in Agile Development 2.0.
Parent Topic:Managing your product development using Agile Development 2.0