> For the complete documentation index, see [llms.txt](https://dev.cubrid.org/dev-process/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dev.cubrid.org/dev-process/dp-en/jira-guide/confirmed.md). # Confirmed: Issue Triage ![](https://dev.cubrid.org/~gitbook/image?url=https%3A%2F%2F2436179334-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-MXop1o57DgerzWA1Brs-2601311391%252Fuploads%252FG2clozWmc5iDIcSc8toh%252F%25E1%2584%2589%25E1%2585%25B3%25E1%2584%258F%25E1%2585%25B3%25E1%2584%2585%25E1%2585%25B5%25E1%2586%25AB%25E1%2584%2589%25E1%2585%25A3%25E1%2586%25BA%25202024-04-26%2520%25E1%2584%258B%25E1%2585%25A9%25E1%2584%2592%25E1%2585%25AE%25203.41.03.png%3Falt%3Dmedia%26token%3D5b6afa31-d4bd-41ab-b074-4b06c5dd4a3d\&width=768\&dpr=1\&quality=100\&sign=2c5f735c4923736de0f0260407bcb80742c2a5dae67261cc5d8e8f2c0c4f54bd) 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. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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, and the optional `goal` query parameter: ``` GET https://dev.cubrid.org/dev-process/dp-en/jira-guide/confirmed.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.