# Resolved: Completing the Task

![](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%252FYRnQML9dwqj8zcuCICK7%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-29%2520%25E1%2584%258B%25E1%2585%25A9%25E1%2584%258C%25E1%2585%25A5%25E1%2586%25AB%25209.04.29.png%3Falt%3Dmedia%26token%3Ddece6a3a-c8fb-431c-ac7d-4e20a86a4a4a\&width=768\&dpr=1\&quality=100\&sign=59f6d7f8a93f64dd5edd87354d153a984218a6cbb792215c3df143283c056353)

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.


---

# 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/resolved.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.