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

Confirmed: Issue Triage

PreviousOpen: Register a JIRA issueNextAnalysis, Develop: Progress of Work

Last updated 12 months ago

Was this helpful?

The project maintainer changes the status from Open to Confirmed through the Triage process. At this point, the following fields are specified:

  • assignee: developer in charge of the issue

  • planned version/s: the version/s in which the issue is planned to be addressed

  • priority: set based on the importance of the issue

  • triage: always set to 'Approved' when transitioning to the Confirmed status

  • labels: Freely set the labels as you need

QA maintainers and test handler can revert an issue from the Resolved status to Confirmed status by pressing the "QA Not Satisfied" button if the issue fails the QA test, or a specification change is needed.

The assignee of the issue can revert an issue from Analysis or Develop status to Confirmed status by pressing the "stop work" button if the issue can no longer proceed due to other tasks.