返回提示词目录第 1407 页

将问题反馈整理为缺陷报告

把零散故障反馈整理成含复现步骤、环境与影响的缺陷报告,并列出待补充信息。

完整提示词

<context>
Engineers can fix a bug quickly when they can reproduce it and know how much it matters. Reports from support, testers and colleagues often arrive as stories ("it keeps crashing when I try to pay") that mix symptoms, guesses about causes and frustration. Reports fail when the title is vague, steps skip the state that triggers the bug (logged in as which role, with what data), expected and actual are merged, the environment is missing, impact is "urgent!!" instead of facts, and guesses are written as if they were observations. The person writing may not be technical; the report should be clear without jargon.
</context>

<task>
<raw_report>
{{raw_report}}
</raw_report>
{{#product_context}}
<product_context>
{{product_context}}
</product_context>
{{/product_context}}

1. Separate what was observed from what the reporter believes or guesses. Keep guesses only in Notes for triage.
2. Write a title of at most about 80 characters: where, what goes wrong, under which condition ("Checkout: Pay button does nothing when the cart has a gift card").
3. Environment: product area, app or browser and version, operating system and device, account type or role, region or language, date and time with time zone of the occurrence, and any ids that help find logs (order number, request id) - never passwords or full card numbers.
4. Preconditions and numbered steps: the starting state (logged in as, data present), then one action per step, as specific as the source allows. Mark steps you inferred with "(inferred)".
5. Expected result and actual result, separately, with exact error text in quotes.
6. Frequency (every time, sometimes with a rough rate, once) and whether it was reproduced by someone other than the reporter.
7. Impact: who is affected and how many if known, whether there is a workaround, data loss or money at stake, and a suggested severity using a common scale (blocker, critical, major, minor, trivial) with the reason; the team may override it.
8. Evidence: list attachments mentioned (screenshots, recordings, logs, HAR files) and what each shows.
9. List the questions to ask the reporter that would most help reproduction, at most five, in plain language.
</task>

<constraints>
- Do not invent steps, versions, error text or numbers of affected users; write [X] or "unknown" and ask.
- Do not guess the cause in the report body; put hypotheses in Notes for triage, labelled as such.
- Remove personal data from the report: names, emails, phone numbers, addresses, payment details. Keep an internal reference to the ticket instead.
- If the report describes several different problems, split them into separate reports.
- If it is a feature request or a question rather than a bug, say so and suggest where it belongs.
</constraints>

<output_format>
## Bug report
Title, then labelled fields: Environment, Preconditions, Steps to reproduce (numbered), Expected, Actual, Frequency, Impact and suggested severity, Evidence, Ticket reference.
## Questions for the reporter
Numbered, plain language.
## Notes for triage
Bullets: hypotheses, related known issues, anything that suggests a recent release caused it.
</output_format>

可替换内容

  • {{raw_report}}
  • {{#product_context}}
  • {{product_context}}
  • {{/product_context}}
  • [X]

分类与标签

编程开发、缺陷报告、问题复现、软件测试、故障分级

前往 AI 图片创作