Bug Reports

Help us maintain platform quality by reporting bugs, technical issues, and unexpected behavior that affect your Qlink campaigns and integrations.

How to Report Bugs

Primary Reporting Channels

Support Email

Email: bugs@rytinco.com
Response: Within 24 hours
Best for: Detailed bug reports with screenshots and logs
Template: Use structured bug report format
Tracking: Automatic ticket creation and updates

Emergency Bug Reporting

Security vulnerabilities: security@rytinco.com
Data loss issues: support@rytinco.com

Bug Report Template

Essential Information

Subject: [Component] Brief description of the issue

Account Details:
- Email: your-email@domain.com
- Plan: [Free/Starter/Professional/Enterprise]
- Organization: Your Company Name

Bug Summary:
[One-line description of the problem]

Steps to Reproduce:
1. [First action taken]
2. [Second action taken]
3. [Action that triggers the bug]

Expected Result:
[What should happen]

Actual Result:
[What actually happens]

Environment:
- Browser: [Chrome 118.0, Firefox 119.0, etc.]
- Operating System: [Windows 11, macOS 14, Ubuntu 22.04]
- Device: [Desktop, Mobile, Tablet]
- Screen Resolution: [1920x1080, etc.]

Additional Information:
- Frequency: [Always, Sometimes, Once]
- Impact: [High/Medium/Low]
- Workaround: [If you found one]
- Related Error Messages: [Exact error text]

Attachments:
- Screenshots: [Attach relevant images]
- Error Logs: [Include console output if applicable]
- Network Logs: [For API-related issues]

Bug Categories

Platform Issues

Dashboard problems - UI/UX bugs in the web interface
Authentication issues - Login, logout, and session problems
Account management - Profile, billing, and team management bugs
Performance problems - Slow loading, timeouts, and crashes

Qlink Issues

Generation failures - Qlink not creating properly
Display problems - Incorrect rendering or appearance
Download issues - Export and file format problems
Customization bugs - Styling and design option failures
Bulk operation errors - Mass editing and processing issues

Analytics Bugs

Data accuracy - Incorrect scan counts or metrics
Reporting errors - Dashboard and export problems
Real-time issues - Live data not updating
Geographic data - Location tracking inaccuracies
Filter problems - Data filtering not working correctly

Bug Investigation Process

Initial Triage

Bug verification - Confirm the issue exists
Priority assignment - Classify based on impact
Team routing - Assign to appropriate engineering team
Duplicate check - Identify if already reported
Information gathering - Request additional details if needed

Investigation Steps

Environment setup - Reproduce the issue internally
Root cause analysis - Identify the underlying problem
Impact assessment - Determine scope and affected users
Solution planning - Design fix approach and timeline
Testing strategy - Plan verification and regression testing

Bug Tracking & Updates

Status Tracking

Reported - Bug submitted and acknowledged
Triaged - Priority assigned and team allocated
In Progress - Actively being investigated/fixed
Testing - Fix implemented and under QA testing
Ready for Release - Fix tested and scheduled for deployment
Resolved - Fix deployed and verified working
Closed - Bug confirmed fixed and issue closed

Communication Process

Acknowledgment - Confirmation within defined SLA
Status updates - Regular progress notifications
Resolution notification - When fix is deployed
Follow-up contact - Verification that issue is resolved
Satisfaction survey - Feedback on support experience

Bug Report Best Practices

Before Reporting

Search existing reports - Check if already reported
Try basic troubleshooting - Clear cache, restart browser
Test in different environment - Try another browser/device
Gather evidence - Take screenshots and note error messages
Document steps - Record exact sequence that causes issue

Effective Bug Reports

Be specific - Include exact error messages and conditions
Provide context - Explain what you were trying to accomplish
Include environment - Browser, OS, device details
Attach evidence - Screenshots, logs, videos if helpful
One bug per report - Don’t combine multiple issues

Security Bug Reports

Responsible Disclosure

Security email: security@rytinco.com
Encryption: PGP key available for sensitive reports
Response time: Within 4 hours for security issues
Coordination: Work with our security team on fixes
Recognition: Security hall of fame for valid reports

Security Bug Information

Vulnerability type - SQL injection, XSS, etc.
Attack vector - How the vulnerability is exploited
Impact assessment - Potential damage or data exposure
Proof of concept - Safe demonstration (don’t exploit)
Recommendations - Suggested fixes if known

Quality bug reports help us maintain a reliable platform. The more details you provide, the faster we can identify and resolve issues.