Have you identified a reproducible problem in an Azure extension for VS Code? Have a feature request? We want to hear about it! Here's how you can make reporting your issue as effective as possible.
Identify Where to Report
There are multiple Azure extensions distributed across different repositories. Try to file the issue against the correct repository:
- Azure Account
- Azure App Service
- Azure Cosmos DB
- Azure Event Grid
- Azure Functions
- Azure Resource Manager
- Azure Storage
- Azure Container Apps
- Docker
Look For an Existing Issue
Before you create a new issue, please do a search in open issues to see if the issue or feature request has already been filed.
If you find your issue already exists, make relevant comments and add your reaction. Use a reaction in place of a "+1" comment:
- 👍 - upvote
- 👎 - downvote
If you cannot find an existing issue that describes your bug or feature, create a new issue using the guidelines below.
Writing Good Bug Reports and Feature Requests
File a single issue per problem and feature request. Do not enumerate multiple bugs or feature requests in the same issue.
Do not add your issue as a comment to an existing issue unless it's for the identical input. Many issues look similar, but have different causes.
The more information you can provide, the more likely someone will be successful at reproducing the issue and finding a fix.
Please include the following with each issue:
-
Version of VS Code
-
Your operating system
-
Version of the relevant VS Code extension
-
Reproducible steps (1... 2... 3...) that cause the issue
-
What you expected to see, versus what you actually saw
-
Images, animations, or a link to a video showing the issue occurring
-
A code snippet that demonstrates the issue or a link to a code repository the developers can easily pull down to recreate the issue locally
- Note: Because the developers need to copy and paste the code snippet, including a code snippet as a media file (i.e. .gif) is not sufficient.
-
Errors from the Dev Tools Console (open from the menu: Help > Toggle Developer Tools)
Final Checklist
Please remember to do the following:
-
Search the issue repository to ensure your report is a new issue
-
Simplify your code around the issue to better isolate the problem
Don't feel bad if the developers can't reproduce the issue right away. They will simply ask for more information!
Automated Issue Management
We use a bot to help us manage issues. This bot currently:
- Automatically closes any issue marked
needs more info
if there has been no response in the past 14 days. - Automatically locks issues 45 days after they are closed.
If you believe the bot got something wrong, please open a new issue and let us know.