Azure / Azure/azure-sdk-tools

AzSDK Tools send users to Issue/Feedback Form

Open
#13,376 0 comments 0 reactions 0 assignees View on GitHub
AzSDK Tools Agent dev inner loop
Dominant language
C#
Stars
135
Forks
260
Avg merge
3d 1h
Merged PRs (30d)
143

Description

We should think about in what cases should the Azure SDK Tools Agent (Copilot + MCP) send a user to open an issue in our repo and when should the agent send them to the feedback form?

I believe the GitHub issues will be for effective for users to report bug and failures with the agent. Issues are a better method for users to give us their chat log to help recreate the issue.

I believe that the feedback form should be more generally used at the end of a major task. This way the results from the feedback form can show an unbiased report of user satisfaction. Whereas if we asked anyone having an issue or running into a bug to fill out the feedback form, our results would skew negative.

Contributor guide

Open the contributing guide

Research direction

No files, tests, or entry points are identified. Start by locating the Azure SDK Tools Agent's handling for GitHub issue and feedback-form links, then clarify the expected routing for agent bugs, failures, chat logs, and post-task satisfaction feedback. Done should be an agreed, documented policy with the corresponding behavior identified.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure
Domain
tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.