---

title: Report Issues language: en description: “Official channels for reporting bugs or sending suggestions to Apache Doris: mailing list and GitHub Issue, with writing tips for high-quality issue reports.” keywords: - Apache Doris issue feedback - Doris bug report - Doris GitHub Issue - dev@doris.apache.org - Doris mailing list feedback - Submit Issue - Reproduction steps

Issue Feedback

If you discover a bug, a performance issue, or want to suggest a feature while using Apache Doris, you can report it to the community through the mailing list or GitHub Issue. This page explains the two official feedback channels and the key information a high-quality report should include.

Feedback Channel Reference

Choose a channel based on the issue type:

Channel	Applicable Scenario	Entry Point
Mailing list	Usage questions, design discussions, community topics	Send an email to dev@doris.apache.org (subscription required first)
GitHub Issue	Reproducible bugs, specific feature suggestions, documentation issues	https://github.com/apache/doris/issues/new/choose
Security vulnerability	Security issues (do not disclose publicly)	See Security Vulnerability Disclosure

Feedback Methods

Method 1: Mailing List

1. Send an email with any subject and content to dev-subscribe@doris.apache.org, and follow the instructions to complete the subscription (see Subscribe to the Mailing List for details).
2. After the subscription is confirmed, send an email to dev@doris.apache.org describing the issue or suggestion.

Method 2: GitHub Issue

Visit the New Issue page, and submit a Bug Report or Feature Request using the template.

Key Points for High-Quality Feedback

To help the community locate the issue quickly, include the following information in your report:

• Describe the issue in detail: Provide logs, key error messages, and the troubleshooting and analysis you have already performed.
• Minimize the issue: Narrow the scope, and strip away business context that is unrelated to the issue.
• Provide reproduction steps: Attach the minimum SQL, configuration, or script that reproduces the issue.
• Focus on the issue itself: Decouple from the business or scenario as much as possible. If scenario information must be retained, provide clear and explicit context.

Related Links

• Subscribe to the Mailing List: Complete the dev mailing list subscription in 5 steps.
• Security Vulnerability Disclosure: Report security issues through the ASF process.
• Join the Community: Other channels including Slack, Twitter, and LinkedIn.