Resolved: Completing the Task

After completing the tasks ("HANDOVER", "BACKPORT"), the Assignee presses the "Check-in Fix" button to change the status to "RESOLVED" and transfers the issue to the QA maintainer. After the transfer to QA, the developer and QA handler communicate through issue comments.

When changing to the "RESOLVED" status, the following fields must be completed:

  • QA assignee: Automatically assigned, no changes needed. (Default: QA maintainer)

  • Resolution: "Done"

  • manual: Indicates whether manual creation or modification is required. (need manual)

  • QA scenario

    • not required: No additional QA scenario needed (default)

    • required: Additional QA scenario needed

    • revise required: Modifications needed for an existing QA scenario

  • Fix version/s: Specifies the version in which the issue was merged (this field is referenced by the QA team for testing and release).

The QA maintainer assigns a QA assignee. If the QA assignee can no longer test the issue due to other tasks, they can press "Stop Test" button to change the status back to "RESOLVED".

The project maintainer can change the status to "RESOLVED" by pressing the "Bug Invalid" button if an issue screened as "OPEN" is determined not to be a bug. Similarly, if the Assignee (the developer in change) determines during the issue progression ("CONFIRMED", "ANALYSIS", or "DEVELOP") that no changes are necessary, they can press the "Resolve without fix" button to change the status to "RESOLVED". Subsequently, the QA maintainer can either change the status to "CLOSED" to conclude the issue or reassess and revert it to "OPEN" if it is deemed as a bug.

Last updated