Rejecting a Defect Action

During the Evaluate, Open, or Test state, the assignee may decide that the actions defined in the defect action are not required or needed, or may not resolve the issue. Rejecting the defect action prevents further work from being done on it.

Required access roles:

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

  1. Do one of the following:
    1. View the Properties page for the defect action. See Defect Action Properties.
    2. From toolbar, click To Rejected .

    Or:

    1. View the list of defect actions for a defect. See Defect Actions Page.
    2. Select the defect actions you want to reject.
    3. From the page toolbar, click Mass Reject . If you select this option, the reason for rejection and notes will be entered for all selected defect actions.
  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 action is being rejected in the Notes text 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 text 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 action 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 action is being rejected.
  4. Click Done.

The defect action is promoted to the "Rejected" state. If all other defect actions for the defect are also in the "Rejected" state, then the defect itself is rejected. If all other defect actions are either rejected or closed, with at least one defect action in the "Closed" state, then the defect itself is promoted to "Closed". If the defect action is later re-evaluated and promoted, Defect Management enters either N/A or removes the reason for rejection.