jira-draftlisted

# Draft a CUBRID JIRA issue Write a ready-to-paste CUBRID JIRA issue from the current work. **Title in concise English; section headers in English; body in Korean.** The **Description** reads as plain, easy-to-understand prose (a reader new to the issue should get it); the **other sections are 개조식** (bullet points, 핵심만). This produces a draft only. You paste it into JIRA; the skill does not post. ## Step 1: Pick the type - **bug**: something is broken / misbehaving. - **task**: non-bug work (개선 / 기능 / 일반 작업). Infer from the context; ask only if it is genuinely unclear. ## Step 2: Gather the facts Pull the specifics from the session (or ask the user): - bug: 증상, 빌드/버전, 재현 절차, 기대 vs 실제. - task: 무엇을·왜, 사양 변경 여부, 구현 방향, 완료 조건. Do not invent. If a field is unknown, write `(확인 필요)` rather than guessing. (Optional: verify CUBRID behavior or terms with **cubrid-manual** before asserting.) ## Step 3: Write the draft **Title (English, concise):** `[<AREA>] <short summary>`: one line, specific, no trailing period. Example: `[JDBC] getObject(LocalDateTime) throws on TIMESTAMP column`. **Body (Korean, 개조식)** under the English headers for the chosen type: ### bug ```markdown ## Description 처음 보는 사람도 이해할 수 있게 문제 상황을 서술체로 설명 (한두 문단) ## Test Build - 빌드/버전/브랜치 (예: 11.3 latest, commit abc123) ## Repro - 재현 절차 1 - 재현 절차 2 ## Expected Result - 기대 동작 ## Actual Result - 실제 동작 (에러/로그 요약) ## Additional Information - (선택) 로그, 환경, 참고 링크 ``` ### task ```markdown ## Description 이 작업이 무엇이고