Contribution Guidelines
en-cg
en-cg
  • Overview
  • Preface
    • How to Read This Document
  • Workflow with JIRA Issues
    • Introduction
    • Open: Register a JIRA issue
    • Confirmed: Issue Triage
    • Analysis, Develop: Progress of Work
    • Handover: Cleaning Up the Task
    • Resolved: Completing the Task
    • Test: Testing
    • Backport: Backporting
    • Closed: Terminating Issues
  • Workflow with Github
    • Introduction
    • Git Workflow
    • Git Branch Model
    • Feature Branch
    • Pull Request, Code Review, Code Merge
    • Backport
  • Workflow after Code Merging
    • Checking the QA Report
    • Procedure Guide in case of Test Failure (Regression)
    • Manual Creation Guide
  • Contributing Guideline for First Contributors
    • Contributor License Agreement (CLA)
    • Good first issue
    • Communication Channel
  • Release
    • Release
Powered by GitBook
On this page

Was this helpful?

Export as PDF
  1. Workflow with JIRA Issues

Resolved: Completing the Task

PreviousHandover: Cleaning Up the TaskNextTest: Testing

Last updated 1 year ago

Was this helpful?

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.