From 3261a2a0b1c4cceb0bc166e54acf1d19d6026664 Mon Sep 17 00:00:00 2001 From: Tak Hoffman <781889+Takhoffman@users.noreply.github.com> Date: Wed, 18 Mar 2026 23:46:45 -0500 Subject: [PATCH] Tighten bug report grounding guidance --- .github/ISSUE_TEMPLATE/bug_report.yml | 46 ++++++++++++--------------- 1 file changed, 21 insertions(+), 25 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/bug_report.yml b/.github/ISSUE_TEMPLATE/bug_report.yml index 3be43c6740a..25fdcc0c805 100644 --- a/.github/ISSUE_TEMPLATE/bug_report.yml +++ b/.github/ISSUE_TEMPLATE/bug_report.yml @@ -7,7 +7,8 @@ body: - type: markdown attributes: value: | - Thanks for filing this report. Keep it concise, reproducible, and evidence-based. + Thanks for filing this report. Keep every answer concise, reproducible, and grounded in observed evidence. + Do not speculate or infer beyond the evidence. If a narrative section cannot be answered from the available evidence, respond with exactly `NOT_ENOUGH_INFO`. - type: dropdown id: bug_type attributes: @@ -23,35 +24,35 @@ body: id: summary attributes: label: Summary - description: One-sentence statement of what is broken. - placeholder: After upgrading to , behavior regressed from . + description: One-sentence statement of what is broken, based only on observed evidence. If the evidence is insufficient, respond with exactly `NOT_ENOUGH_INFO`. + placeholder: After upgrading from 2026.2.10 to 2026.2.17, Telegram thread replies stopped posting; reproduced twice and confirmed by gateway logs. validations: required: true - type: textarea id: repro attributes: label: Steps to reproduce - description: Provide the shortest deterministic repro path. + description: Provide the shortest deterministic repro path supported by direct observation. If the repro path cannot be grounded from the evidence, respond with exactly `NOT_ENOUGH_INFO`. placeholder: | - 1. Configure channel X. - 2. Send message Y. - 3. Run command Z. + 1. Start OpenClaw 2026.2.17 with the attached config. + 2. Send a Telegram thread reply in the affected chat. + 3. Observe no reply and confirm the attached `reply target not found` log line. validations: required: true - type: textarea id: expected attributes: label: Expected behavior - description: What should happen if the bug does not exist. - placeholder: Agent posts a reply in the same thread. + description: State the expected result using a concrete reference such as prior observed behavior, attached docs, or a known-good version. If no grounded reference exists, respond with exactly `NOT_ENOUGH_INFO`. + placeholder: In 2026.2.10, the agent posted replies in the same Telegram thread under the same workflow. validations: required: true - type: textarea id: actual attributes: label: Actual behavior - description: What happened instead, including user-visible errors. - placeholder: No reply is posted; gateway logs "reply target not found". + description: Describe only the observed result, including user-visible errors and cited evidence. If the observed result cannot be grounded from the evidence, respond with exactly `NOT_ENOUGH_INFO`. + placeholder: No reply is posted in the thread; the attached gateway log shows `reply target not found` at 14:23:08 UTC. validations: required: true - type: input @@ -92,12 +93,6 @@ body: placeholder: openclaw -> cloudflare-ai-gateway -> minimax validations: required: true - - type: input - id: config_location - attributes: - label: Config file / key location - description: Optional. Relevant config source or key path if this bug depends on overrides or custom provider setup. Redact secrets. - placeholder: ~/.openclaw/openclaw.json ; models.providers.cloudflare-ai-gateway.baseUrl ; ~/.openclaw/agents//agent/models.json - type: textarea id: provider_setup_details attributes: @@ -111,27 +106,28 @@ body: id: logs attributes: label: Logs, screenshots, and evidence - description: Include redacted logs/screenshots/recordings that prove the behavior. + description: Include the redacted logs, screenshots, recordings, docs, or version comparisons that support the grounded answers above. render: shell - type: textarea id: impact attributes: label: Impact and severity description: | - Explain who is affected, how severe it is, how often it happens, and the practical consequence. + Explain who is affected, how severe it is, how often it happens, and the practical consequence using only observed evidence. + If any part cannot be grounded from the evidence, respond with exactly `NOT_ENOUGH_INFO`. Include: - Affected users/systems/channels - Severity (annoying, blocks workflow, data risk, etc.) - Frequency (always/intermittent/edge case) - Consequence (missed messages, failed onboarding, extra cost, etc.) placeholder: | - Affected: Telegram group users on - Severity: High (blocks replies) - Frequency: 100% repro - Consequence: Agents cannot respond in threads + Affected: Telegram group users on 2026.2.17 + Severity: High (blocks thread replies) + Frequency: 4/4 observed attempts + Consequence: Agents do not respond in the affected threads - type: textarea id: additional_information attributes: label: Additional information - description: Add any context that helps triage but does not fit above. If this is a regression, include the last known good and first known bad versions. - placeholder: Last known good version <...>, first known bad version <...>, temporary workaround is ... + description: Add any remaining grounded context that helps triage but does not fit above. If this is a regression, include the last known good and first known bad versions when observed. If there is not enough evidence, respond with exactly `NOT_ENOUGH_INFO`. + placeholder: Last known good version 2026.2.10, first known bad version 2026.2.17, temporary workaround is sending a top-level message instead of a thread reply.