Rejecting a Defect

Rejecting a Defect means that the Change Board disagrees that the problem is a defect that needs to be fixed. You can only reject the Defect when it is in the Open state and if no Defect Actions have been promoted beyond the Evaluate state.

If work has started on Defect Actions and you want to reject the Defect, you need to reject each of the Defect Actions, and Defect Management automatically rejects the Defect. See Rejecting a Defect Action.

Before you begin: View the Properties page for the Defect. See Viewing Defect Details.

  1. From the page toolbar, click Promote to Rejected.

    If the Defect has at least one Defect Action associated with it that has been promoted to the Closed state, then the Defect cannot be rejected.


    Promote to Rejected

  2. From the Reason for Rejection list, select why the Defect is rejected:

    • User Error. No Defect exists; explain why the user encountered this problem in the Notes box.
    • Duplicate. This Defect has already been reported. (This option is the same as using the Mark as Duplicate action).
    • Unreproducible. The problem could not be reproduced.
    • Enhancement. The problem is not an actual Defect, but a request for functionality to be added to the product.
    • No Plan. The Defect is acknowledge, but there is no plan for fixing it, either because the problem occurs rarely or has no real effect on usability.
    • N/A. None of the above reason is appropriate. Enter the reason why this Defect is being rejected in the Notes box.

  3. In the Notes box, enter an explanation for why the Defect is being rejected.

  4. Click Done.

All Defect Actions associated with the Defect are also demoted to the Rejected state. If the Change Board decides at a later time to accept the defect (promotes from Evaluate to Open), the Reason for Rejection field is cleared, and the Notes field retains the notes.