🐛Bug Reporting

How to properly report bugs and technical issues for fastest resolution

How to Report Bugs Effectively

The best way to report a bug is to create a support ticket inside the Discord server. This ensures your report is properly tracked and prioritized by our development team.

---

Steps to Create a Bug Report Ticket

1. Join Discord Server: https://discord.gg/DxXQ4HdnES

2. Navigate to: #create-ticket channel

3. Click: "Create Support Ticket" button

4. Select: "Bug Report" category

5. Provide Details: Follow the template below

---

Bug Report Template

When creating your ticket, include these essential details:

🐛 BUG REPORT

EA Version: v4.4.6 (or dev version)
MT4 Build: 1090 (Help → About in MT4)
Broker: [Your broker name]
Symbol: EURUSD (or symbol where bug occurred)
Timeframe: M5/H1/etc.

DESCRIPTION:
[Clear description of what went wrong]

EXPECTED BEHAVIOR:
[What should have happened]

ACTUAL BEHAVIOR:
[What actually happened]

STEPS TO REPRODUCE:
1. [First step]
2. [Second step]
3. [Result]

ERROR MESSAGES:
[Copy exact error text from Experts tab]
[Screenshot if possible]

SETTINGS:
[Screenshot of EA inputs tab]

ADDITIONAL INFO:
[Any other relevant details]

---

What Makes a Good Bug Report

Do Include ✅

Specific Details

• Describe exact steps to reproduce the issue

• Include version numbers (EA, MT4, broker platform)

• Specify exact symbol and timeframe

Complete Information

• Include all requested information from template

• Provide screenshots of error messages

• Share your EA settings (screenshot of inputs tab)

Error Logs

• Copy exact error messages from Experts tab

• Include timestamp of when error occurred

• Mention any unusual market conditions

Reproducibility

• Confirm the bug happens consistently

• Note if it happens with specific settings only

• Mention if it occurs on multiple symbols

Don't Do ❌

Vague Descriptions

• "EA doesn't work" - too general

• "Something is broken" - no details

• "It's not trading" - missing context

Missing Information

• No EA version number

• No error messages or screenshots

• No description of settings used

Wrong Channels

• Reporting via DM instead of tickets

• Posting in general chat without ticket

• Emailing without creating ticket first

---

Bug Report Priority Levels

🔴 Critical (Fixed within 24-48 hours)

Examples:

• EA crashes MT4

• Data loss or corruption

• Major calculation errors

• Security vulnerabilities

• Account cannot trade at all

What to expect:

• Immediate acknowledgment

• Developer assigned within hours

• Hotfix deployed quickly

• You'll be notified of progress

🟡 High (Fixed within 1 week)

Examples:

• Feature not working as documented

• Significant performance issues

• Incorrect trade execution

• Settings not saving properly

What to expect:

• Response within 24 hours

• Investigation started immediately

• Fix included in next patch release

• You'll receive update notifications

🟢 Medium (Fixed in next update)

Examples:

• Minor calculation discrepancies

• UI/visual issues

• Documentation errors

• Non-critical feature bugs

What to expect:

• Response within 48 hours

• Scheduled for next version

• Fix bundled with other updates

• Listed in changelog

🔵 Low (Scheduled for future release)

Examples:

• Feature requests

• Cosmetic improvements

• Nice-to-have enhancements

• Minor UI polish

What to expect:

• Acknowledged and logged

• Considered for roadmap

• May be included in major updates

• Community feedback influences priority

---

After Reporting

What Happens Next

1. Ticket Created ✅

   • You'll receive confirmation message

   • Ticket assigned unique ID number

   • Status set to "New"

2. Initial Response 👀

   • Team reviews within 24 hours

   • Priority level assigned

   • Developer assigned if critical

3. Investigation 🔍

   • We may request additional information

   • You might be asked to test scenarios

   • We'll provide status updates

4. Resolution 🔧

   • Fix implemented and tested

   • Internal testing completed

   • Beta testers may verify fix

5. Notification 📢

   • You'll be notified when fix is available

   • Changelog updated with fix details

   • New version released

6. Verification ✔️

   • Please test and confirm fix works

   • Provide feedback on resolution

   • Ticket closed when confirmed

---

Common Bug Reporting Mistakes

Mistake #1: Not Enough Information

Bad Example:

"EA stopped working, please fix"

Good Example:

"EA (current version) on EURUSD M5 stopped opening trades after 10 AM GMT. Error log shows 'ERR_TRADE_DISABLED'. Settings attached. This started on Nov 21, 2025."

Mistake #2: Reporting in Wrong Place

Bad Example:

• Posting in #general-chat

• DMing moderators directly

• Emailing without ticket reference

Good Example:

• Create ticket in #create-ticket channel

• Use proper Bug Report category

• Include all required information

Mistake #3: Multiple Issues in One Report

Bad Example:

"EA has wrong colors, trades close early, and I can't change settings"

Good Example:

• Create separate ticket for each issue

• Prioritize most critical problem first

• Link related tickets if necessary

---

Emergency Bug Reporting

When to Use Emergency Process

Only for critical issues that:

• Completely prevent EA from functioning

• Cause financial loss or risk

• Affect account security

• Prevent access to trading

Emergency Contact

Discord: @Moderator ping in general channel

Email: Mark subject line "URGENT - BananaEA Critical Issue"

Response: Within 4 hours

---

Next Steps: Learn about Discord Community Guide or review Technical Support Levels.