Report an Issue
Found a bug, experiencing an error, or have a feature request? We want to hear about it! Your reports help us improve MangoLabs for everyone. This guide shows you how to report issues effectively so we can address them quickly.
Your Reports Matter
Every bug report, feature request, and piece of feedback helps us build a better platform. We read and prioritize all reports. Thank you for taking the time to help improve MangoLabs!
Before Reporting
Quick Checklist
Your issue might already be answered in the FAQ section.
Check if someone else already reported it on GitHub Issues or Discord.
Refresh page, clear cache, try different browser. Sometimes simple fixes resolve issues.
Screenshots, error messages, steps to reproduce - collect details before reporting.
Types of Reports
Bugs & Errors
Something's broken, not working as expected, or showing error messages.
Data Issues
Incorrect prices, missing features, calculation errors, or outdated market data.
Feature Requests
Ideas for new features, indicators, improvements, or workflow enhancements.
GitHub Issues (Recommended)
Report on GitHub
Our preferred method for bug reports and feature requests. GitHub issues are tracked publicly, searchable, and allow community discussion.
Free account at github.com/join
Choose template: Bug Report or Feature Request
Provide all requested information (see guidelines below)
Team will respond, ask for clarification, or mark for fixing
Discord Support
Report on Discord
For quick questions, urgent issues, or when you need community input. Discord provides faster initial response but is less organized for long-term tracking.
- • Urgent bugs affecting trading
- • Quick clarification questions
- • Getting community feedback on issues
- • Account-specific problems
- • #help-support - General issues and questions
- • #bug-reports - Bug reporting
- • #feature-requests - Feature ideas
Writing Effective Bug Reports
Essential Information to Include
1. Clear Title
Good: "Backtest fails with 'Feature not found' error when using RSI_14"
Bad: "It's broken" or "Help!!!"
2. Steps to Reproduce
Numbered list of exact steps:
- 1. Navigate to Strategy Builder
- 2. Create new strategy named "Test"
- 3. Add RSI_14 feature node
- 4. Connect to comparison node
- 5. Click "Validate Strategy"
- 6. Error appears: "Feature not found"
3. Expected vs Actual Behavior
Expected: Strategy should validate successfully
Actual: Error message "Feature not found" shown, validation fails
4. Environment Details
- • Browser: Chrome 120.0.6099.129
- • Operating System: Windows 11
- • Account: email@example.com
- • Date/Time: 2024-01-15 14:30 UTC
5. Screenshots/Videos
Include screenshots of errors, unexpected behavior, or console logs (F12 → Console tab). Videos help for complex issues.
6. Error Messages
Copy full error text, not just screenshots. Include browser console errors (F12 → Console):
at StrategyBuilder.jsx:145
Writing Feature Requests
How to Propose New Features
What pain point does this solve? "Currently, I have to manually check 5 different pages to see all my paper trading performance. This is time-consuming."
What would you like to see? "A unified dashboard showing all paper trading accounts, their P&L, and active strategies in one view."
Who benefits and how? "All users with multiple paper trading accounts would save time. Makes monitoring easier, especially for managing diverse strategies."
Mockups, sketches, or examples from other platforms that do this well.
What to Expect
Critical Bugs
Platform down, data loss, security issues
Response: <24 hours
Fix: 1-3 days
Major Bugs
Features broken, incorrect calculations, workflow blockers
Response: 1-3 days
Fix: 1-2 weeks
Minor Issues & Features
UI bugs, enhancement requests, nice-to-haves
Response: 1 week
Fix: Varies (roadmap)
After Reporting
Monitor Your Issue
GitHub sends email notifications when team responds. Watch for requests for additional information or clarification.
Provide Additional Details
If team asks for more info, respond promptly. More details = faster resolution.
Test Fixes
When issue is marked as fixed, test it and confirm resolution. Report if problem persists.
Thank You!
Every bug report, no matter how small, helps us improve MangoLabs. Your time and effort in reporting issues is genuinely appreciated. Together, we're building a better trading platform for everyone.