Manage Defects

Print this topicEmail this topic

A defect, or bug, is an error, flaw, mistake, failure, or fault in software that prevents it from behaving as intended, such as producing an incorrect result. You can create, manage, and track defects in Rally.

Managing defects includes the following:

Create a defect


Concurrency conflicts may occur if multiple users edit the same defect. The first user to make their changes and click any of the Save options will have their changes committed. When subsequent users make their changes to the same defect then attempts to save, they are presented with an option to Review my changes or Overwrite with my version.

If you select Review my changes, you are returned to the defect editor so the changes can be copied and not lost. If you select Overwrite with my version, your changes are saved and the other user's changes are overwritten. Overwrite with my version where attachments are added and edited will save both users' changes as well as apply deletions.

Edit a defect

With the editor

  1. Click the edit icon Inline Edit of the defect you want to edit.
  2. In the Create Defect editor, complete your edits.
  3. Select one of the Save options.

Inline edit

  1. Double-click a defect row to invoke edit mode.
  2. Complete your edits.
  3. Click Inline Save to save your defect or click Cancel to cancel.

Manage duplicate defects

Sometimes a defect is inadvertently entered into the system more than once. You can associate, then close, any duplicate defects to the single defect you want to keep open.

Add duplicate defects

To associate duplicate defects to the defect you wish to keep:

  1. Select the defect you wish to keep on the Defects summary page.
  2. From the Defect detail page, click the Duplicates link in the sidebar.
  3. From Actions select Add Duplicates.
  4. On Choose Duplicates, select all the defects that should be identified as duplicates.
  5. Select Choose.

    The selected defects display on the Duplicates page.

    Note: On the chooser page, if you select items and then click to the next page , your selections on the first page are not saved. Filter your search criteria and increase your display to limit your results to one page.

Remove duplicate defects

Once you close a duplicate defect, you may wish to remove its association with the original defect.

  1. Select the defect you wish to keep on the Defects summary page.
  2. From the Defect detail page, click the Duplicates link in the sidebar.
  3. From Actions, select Remove Duplicates.
  4. On Choose Duplicates, select all the associated defects you wish to remove.
  5. Select Choose.

    The selected defects are removed from the display.

    Note: On the chooser page, if you select items and then click to the next page , your selections on the first page are not saved. Filter your search criteria and increase your display to limit your results to one page.

Navigate between duplicate defects

Use this method to quickly navigate to the duplicate defect to close it.

  1. Click the Name link of the duplicate defect.
  2. On the detail page of the duplicate defect, click the Duplicates link in the sidebar to return to the original defect.

Convert a defect to a user story

Convert defects that are enhancement requests to a user story from the Defect detail page. This allows you to close the defect and create a user story in one action.

Before converting defects to user stories, be aware of the following:

  • The defect's tasks, attachments, and test cases will be associated with the new user story and the defect will be closed.
  • The only test cases that will be associated with the new user story are those that have the defect listed in the test case's Work Item field.
  • If a test case is listed in the Test Case field of the of the defect, the test case will not be associated to the user story.

From the Defect detail page

  1. Select the defect you wish to convert on the Defects summary page.
  2. From the Defect detail page, click Actions, then Convert to User Story.
  3. Click OK to close the defect and create an unscheduled user story.

Field conversion information:

  • Resolution is changed to Converted.
  • Schedule information is included in the new user story.
  • Defect fields that do not exist in a user story are stored in the Notes field as name-value pairs.
  • Custom Fields are stored in the Notes field as name-value pairs.
  • If there are required custom fields for user stories, an editor displays. Fill out the required fields to complete the conversion.
  • Salesforce.com Integration custom fields are included if present: Number of Cases, Affected Customers, and Salesforce Case.
  • Discussions created in Salesforce.com Integration are included if present.
  • Defect revision history is preserved.

Schedule defects

When planning work for each iteration, select defects from the backlog and schedule them into an iteration or release.

From the Plan page

  1. Click the Plan tab, then the Plan page.
  2. Select the Show Defects icon .
  3. Click the defect and drag it into the desired release backlog or iteration.

    The related scheduled fields on the defect detail page are updated to reflect the scheduling information.

From the Defect detail page

  1. Select the defect you wish to schedule on the Defects summary page.
  2. On the Defect detail page, click Actions, then Edit.
  3. On the defect editor, choose an iteration or release from the drop-down listings.
  4. Click Save.
  5. You can view the scheduled defect in the related Iteration Status or Release Status pages.

Delete defects

  1. Select the defect you wish to delete on the Defects summary page.
  2. On the Defect detail page, click Actions, then Delete.

The defect is placed in the recycle bin.

My Defects

My Defects is an app you can add to your personalized dashboard. Only defects for which you are the owner display in the app.

Use the My Defects app to arrange your defects into a meaningful display. Click the Settings icon in the upper-right corner to specify project, columns, order, and add queries to customize your view. You can double-click in a field for inline editing.

For more information on this app, see the App section of the help.

Use the Defect summary and detail pages

Summary page

The Defects summary page provides a summary listing of all defects in your selected workspace and project.


At the top of the summary page is a mini Defect Arrival and Kill Rate chart. The header displays the start and end dates of the current iteration. Click anywhere on the mini chart to display the full-sized chart.

From the summary page, you can:

  • Select a custom or quick view to group your defects into a meaningful display.
  • Perform the common actions of all work item summary pages.
  • Select the Edit , Copy icon , or Add to Defect Suite icons to edit an individual defect.
  • Inline edit a defect.

Detail page

The Defect detail page provides a view of an individual defect.  

When you access the Defect detail page from a sidebar link from the User Story detail page, the Defects page displays all of the defects directly associated with the user story and its child stories. This allows you to work with all of the defects that directly or indirectly affect the user story.

From the detail page, you can:

  • View all the details of a single defect, including all current field values and any custom fields that are available for your workspace.
  • Use the sidebar to link to any associated artifacts related to the current defect.
  • Use the Actions menu to select options such as Edit, New, Copy, Print, Delete, Convert to User Story, and other specific actions directly from the detail page.

Defect fields

The following fields are available to help you describe or add detail to a defect. You can set these field values when creating or editing a defect.

Required fields are highlighted in red on the full screen editor.

Field Description
General
ID A system-generated ID that is assigned to your defect; it is unique and will never change. The ID consists of a tag prefix and a numerical value. The tag can be customized by your system administrator to reflect a differentiating prefix for each work item defined in your project, such as DE for defect, US for user story, and so on.
Defect
State Select a state from the drop-down. When the state is set to Closed, the date the defect was closed is appended.
Environment Select a value from the drop-down to describe the environment in which the defect was discovered.
Priority Select a value from the drop-down list that indicates the importance of the defect. These values can be customized by your subscription administrator. Defects with a priority 1 or 2 display on the Iteration Defects page.
Severity Select a value from the drop-down list that indicates the importance of the defect. These values can be customized by your subscription administrator. Defects with a severity 1 or 2 display in the Iteration Defects page.
Submitted By This field defaults to the team member that creates the defect.
Creation Date A read-only field that displays the date the defect was created.
Found in Enter the build number in which the defect was found. This field is alphanumeric and supports the use of special characters.
Fixed in Enter the build number in which the defect was resolved. This field is alphanumeric and supports the use of special characters.
Target Build Enter the build number in which the defect is expected to be resolved. This field is alphanumeric and supports the use of special characters.
Verified in Enter the build number in which the defect was verified in. This field is alphanumeric and supports the use of special characters.
Resolution Select a value from the drop-down that best describes the resolution action for the defect.
Release Note/Affects Doc Select either or both of these fields to help track those defects whose resolutions impact the documentation or Release Notes.
User Story Associate the defect with a user story. If you create a defect from another work item, this association is automatically established.
Test Case Associate the defect with a test case. Test case steps are referenced in the Steps display directly below the test case name and are visible only when editing the defect. If the defect was created from a test case, this association is automatically established.
Test Case Results If an association to a test case is specified, the test case results chooser displays below the Test Case Steps field.
Target Date Click the calendar icon and choose a date the defect is expected to be resolved.
Schedule
Schedule State Specify the progress that has been made toward the completion of the defect. There are six values available in the drop-down list. The first and last states can be customized by your subscription administrator to help you better manage your process. The following are default states that the defect can move through:
  • Defined: The development team can write tasks and provide estimates. This is the defaulted state value for a new defect and cannot be customized.
  • In Progress: The defect has been committed to an iteration and work has begun on the defect. This state cannot be customized.
  • Completed: All related tasks have been completed. When the state for all of the tasks are set to Completed, the defect is automatically rolled up to reflect the Completed state regardless of its initial setting. This state cannot be customized.
  • Accepted: The acceptance criteria has been met. This state cannot be customized.
Blocked Work on the defect cannot continue until all issues preventing further progress are removed. If a task has been marked blocked, this field will automatically be checked in the editor. You can also manually block the defect by editing it and selecting the checkbox. The blocked state will display on the Iteration Status or Release Status pages in red to indicate blocked, but will still carry the associated state letter so the initial state of the defect is not lost.
Ready This checkbox can be used to indicate that a defect is ready to move into the next stage of development or review. When using board apps such as the Iteration Tracking Board, the defect will display with a green border in the app. You may set up notifications against the Ready field to be alerted when the field is checked.
Blocked Reason Use this field to notate why progress on the defect is currently blocked.
Release/Iteration These fields indicate the release or iteration to which the defect is assigned. Select a release or iteration in the drop-down to view all available releases or iterations contained in the project.
Plan Estimate Record how much effort is estimated to complete the defect. This field is a real number and can accept three digits followed by a decimal and two more digits. The units are defined by your administrator.
Task Estimate, Actual, and To Do Read-only fields. The values contained in these fields are rolled up from all associated tasks and displayed in the defect.
Custom
Custom Fields Custom fields that have been defined for your workspace are located in this section.
Notes
Notes Use this rich text field for recording additional information associated with the defect.
Revision
Change Description Record any changes made to the defect during an edit. Change Description comments are stored and displayed in the Revision History page.

Feedback

Please send us your feedback regarding our help site. For feedback regarding the Rally product, click here to open a support case or click here to submit a new feature request
English
By submitting this form, you accept the Mollom privacy policy.
© 2014 Rally Software Development Corp | Legal