# Introduction

<figure><img src="https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MXop1o57DgerzWA1Brs-2601311391%2Fuploads%2FZfHmsli3ge50YaSdPDOh%2F%E1%84%89%E1%85%B3%E1%84%8F%E1%85%B3%E1%84%85%E1%85%B5%E1%86%AB%E1%84%89%E1%85%A3%E1%86%BA%202024-04-26%20%E1%84%8B%E1%85%A9%E1%84%92%E1%85%AE%202.50.32.png?alt=media&#x26;token=b45615d0-1b38-440e-bc05-3117e25cb98e" alt=""><figcaption></figcaption></figure>

CUBRID uses JIRA to manage its projects, and all changes are managed on an issue-by-issue basis. JIRA issues can have nine statuses as shown in the diagram: Open, Confirmed, Analysis, Develop, Handover, Backport, Resolved, Test, and Closed, and the status of an issue is updated according to its progress. An issue starts in the Open status and is completed when it reaches Closed.

The primary actor responsible for advancing an issue may vary depending on the status.&#x20;

For instance, in Open status, the project maintainer performs a triage on the issue, approves it, and assigns it to a developer, moving it to Confirmed status.&#x20;

Analysis status involves the developer analyzing the assigned issue, including analysis, design, proof of concept (POC), and peer review of the design before development begins.&#x20;

Develop status involves developing based on the analyzed information, peer reviews, unit testing, and code merging.&#x20;

Handover status is a preparatory stage for transferring to the Quality Assurance (QA) team, including organizing test scenarios, writing manuals, and modifying regression tests.&#x20;

In Resolved status, the QA maintainer assigns the issue to a tester.&#x20;

The designated tester then changes the status to Test and performs QA tasks.&#x20;

Backport status reflects the tested issue's code and manual to a lower version.

However, the project maintainer can make modifications such as content and status transitions at any stage.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://dev.cubrid.org/dev-process/dp-en/jira-guide/intro.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.