Reporting Issues
For comprehensive guidance, see the Bug Reporting & Diagnostics Guide.
Best Method: Use the Built-in Issue Reporter
The fastest and most accurate way to report a bug is directly from your ChurchCRM installation.
Step-by-Step Instructions
- Log in to your ChurchCRM instance.
- Navigate to Support in the top navigation menu.
- Select Report an Issue to open the built-in reporting tool.
- Fill out the form:
- Describe what happened.
- Include steps to reproduce the issue.
- Attach any relevant screenshots.
- Submit the form. The system automatically captures your technical environment and sends the report to the development team.
What Gets Captured Automatically
When you use the in-app reporter, the following information is collected automatically:
- ChurchCRM version (exact version and build)
- Server environment (PHP version, database type, server OS)
- Browser information (user agent, screen size)
- User context (role, permissions, current page)
- System configuration (relevant settings and enabled modules)
- Recent error logs related to your session
This information is essential for diagnosis and significantly speeds up issue resolution.
Alternative: GitHub Issues
Use GitHub issues only if you cannot access ChurchCRM directly.
When to Use GitHub Instead
- You cannot log in (authentication issues)
- ChurchCRM is not yet installed
- The server is completely unreachable
- You are reporting a documentation problem
- You are reporting a development environment issue
GitHub Issue Templates
- Bug Report — For software defects
- Feature Request — For new functionality
- Question — For support questions
Community Support
- GitHub Discussions — Ask questions, share ideas, and find community solutions
Before Reporting
- Search existing issues — your problem may have already been reported.
- Check the documentation — the answer may already be available.
- Try in a different browser — to rule out browser-specific issues.
- Clear your browser cache — stale cached files can cause unexpected behavior.
Information to Include When Reporting via GitHub
- A clear description of what happened
- Steps to reproduce the issue
- Expected versus actual behavior
- Screenshots or error messages
- ChurchCRM version (found in About or System Info)
- Browser and device
Quick Reference
| Goal | Best Option |
|---|---|
| Report a bug | In-app Support → Report Issue |
| Request a feature | GitHub Feature Request |
| Ask a question | GitHub Discussions |
| Report a login issue | GitHub Bug Report |