AI プロンプト

Please concisely summarize the current status of this issue, in order to hand it
over to the next backend engineer on customer support rotation duty for the
Groups & Projects team.

Use this template:

---

A handover comment generated by Duo and reviewed by me:

### Current status

<!-- Content of current status -->

*Confidence: <!-- Percentage confidence level in the accuracy of this status -->*

### Action items

- <!-- GitLab handle of DRI --> (*Confidence: <!-- Percentage confidence in who should be DRI for this item -->*): <!-- Action item -->. (*Confidence: <!-- Percentage confidence in the validity of this action item -->*)

---

- Be sure, or be conservative.
- When making assertions, be wary of hallucinations.
- Use qualifying language as appropriate.
- If you reference a resource with a URL, such as a GitLab issue or Zendesk
  ticket number, then make it a link.
- Read linked URLs if the added context might improve your answer.
- Answer with only Markdown code. I will review it and post it.

Investigate this issue, read the feature docs, suggest possible root causes and
questions to ask the customer.

Identify if any other issues in the `request-for-help` project could be related.

Generate a status update for this Epic using the following format.
The "Achievements" section should highlight any issues closed within the last 7
days since the last status update, with a short (1-2 sentence) summary of what
the issue accomplishes for customers. "Blockers" can be either left empty,
or use any issues whose status is blocked. For the "Next" section, include any
issues that have an assignee and have the status "in dev" or "in review".

---

## <!-- Date in YYYY-MM-DD --> – <!-- Title of Epic -->

<!-- Create a high level summary -->

### :tada: **Achievements**:

- <!-- Content of Achievements -->

### :issue-blocked: **Blockers**:

- <!-- Content of Blockers (optional) -->

### :arrow_forward: **Next**:

- <!-- Content of Next -->

---

- Be sure, or be conservative.
- When making assertions, be wary of hallucinations.
- Use qualifying language as appropriate.
- If you reference a resource with a URL, such as a GitLab issue or Zendesk
  ticket number, then make it a link.
- Read linked URLs if the added context might improve your answer.
- Answer with only Markdown code. I will review it and post it.
- Format the summary in a conversational, readable manner. Avoid business speak.
- You should use markdown for the output and wrap it in backticks.