Conversation
Updated descriptions for actual behavior and reproduction steps to clarify requirements.
joshfree
requested review from
JonathanCrd,
KarishmaGhiya,
chidozieononiwu,
fanyang-mono,
g2vinay and
jairmyree
There was a problem hiding this comment.
Pull request overview
This PR updates the Azure MCP bug report issue template to clarify what information reporters should include for “Actual behavior” and “Reproduction Steps,” improving triage quality and report consistency.
Changes:
- Refines “Actual behavior” guidance to request tool names, prompts used, and error messages.
- Adjusts “Reproduction Steps” example to reference “prompt snippet” rather than “code snippet.”
jongio
left a comment
jongio
left a comment
There was a problem hiding this comment.
Updates MCP-specific language for the Azure bug report template - makes sense.
Note: the Fabric MCP template (10_fabric_mcp_bug_report.yml) and Bug Bash template (01_bug_bash_mcp_report.yml) still have the old wording ("exception stacktraces or memory dumps" / "code snippet"). Worth updating those for consistency, either in this PR or a follow-up.
|
I was thinking of deleting the old bug bash template. Thoughts? |
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
jongio
left a comment
jongio
left a comment
There was a problem hiding this comment.
Clean PR. Checked template changes against MCP context - the new wording matches how users actually interact with MCP servers. LGTM.
What does this PR do?
Updated descriptions for actual behavior and reproduction steps to clarify requirements.