Rejecting a Defect

Rejecting a defect means that the Defect Manager 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.

Required access roles:

  • App-specific: Defect Engineer
  • Baseline: Leader, Author, or Reader

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

Before you begin: View the Properties page for the defect. See Defect Properties.
  1. From the toolbar, click 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.
  2. From the Reason for Rejection drop-down list, select why the defect is rejected:

    ReasonDescription
    N/ANone of the other reasons is appropriate. Enter the reason why this defect is being rejected in the Notes box.
    DuplicateThis defect has already been reported. (This option is the same as using the Mark as Duplicate action).
    User ErrorNo defect exists. Explain why the user encountered this problem in the Notes box.
    UnreproducibleThe problem could not be reproduced.
    EnhancementThe problem is not an actual defect, but a request for functionality to be added to the model version.
    No PlanThe defect is acknowledged, but there is no plan for fixing it, either because the problem occurs rarely or has no real effect on usability.

  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 promoted to the Rejected state. If the Defect Manager decides at a later time to accept the defect (promotes it from "Evaluate" to "Open"), the Reason for Rejection field is cleared, and the Notes field retains the notes.