External Tool Integration
Connect BetaHub with your project management and development tools for streamlined workflows.
Overview
BetaHub integrates with popular project and task management tools to bridge the gap between bug reporting and development workflows. Send entries from BetaHub directly to your preferred project management system.
Supported Platforms
Project Management Tools
- Jira - Atlassian’s issue tracking and project management
- Asana - Team collaboration and task management
- Monday.com - Work operating system and project tracking
- Notion - All-in-one workspace with databases
Development Platforms
- GitHub - Code repository with integrated issue tracking
- Redmine - Open-source project management
Custom Integrations
- API-based - Any system with REST API support
- Webhook - Real-time notifications to external services
Need integration with a different tool? Contact us at hello@betahub.io to discuss your requirements.
Setting Up Integrations
Initial Setup Process
- Access Integration Settings
- Navigate to your project page in BetaHub
- Select Settings from the left sidebar
- Click on Integrations
- Choose Platform
- Select your desired integration (e.g., “Connect with Jira”)
- Follow the connection wizard’s authentication steps
- Configure Authentication
- Provide API credentials or complete OAuth flow
- Test connection to verify access
- Map Fields
- Configure how BetaHub fields translate to external fields
- Set default values and dynamic expressions
- Test with sample data
Platform-Specific Setup
Jira Integration
Prerequisites:
- Jira Cloud or Server instance
- Admin access to create API tokens
- Project permissions for issue creation
Setup Steps:
- Generate API token in Jira
- Provide Jira URL, username, and token
- Select target project and issue type
- Map BetaHub fields to Jira fields
Common Field Mappings:
- Summary ← Bug title
- Description ← Bug description + steps to reproduce
- Priority ← BetaHub priority level
- Labels ← BetaHub tags
GitHub Integration
Prerequisites:
- GitHub repository access
- Personal access token with repository permissions
Setup Steps:
- Generate personal access token on GitHub
- Provide repository owner and name
- Configure issue templates and labels
- Map fields to GitHub issue format
Common Field Mappings:
- Title ← Bug title
- Body ← Formatted description with links
- Labels ← BetaHub tags and priority
- Assignees ← Project developers
Asana Integration
Prerequisites:
- Asana workspace access
- API token or OAuth application
Setup Steps:
- Authenticate with Asana account
- Select workspace and project
- Configure task fields and custom fields
- Set up automatic assignee rules
Common Field Mappings:
- Name ← Bug title
- Notes ← Detailed description
- Priority ← Asana priority levels
- Tags ← BetaHub categories
Field Mapping Configuration
Mapping Modes
BetaHub supports four field mapping modes:
| Mode | Description | Use Case | Example |
|---|---|---|---|
| Not Mapped | Field is skipped | Irrelevant fields | Internal IDs |
| Constant Value | Fixed value used | Default categories | Priority: “High” |
| Map From Field | Direct field mapping | Simple translations | Title → Summary |
| Dynamic Expression | Template-based | Rich formatting | Description with links |
Dynamic Expression Examples
Rich Description Template:
#
**Reporter:**
**Reported:**
## Description
## Steps to Reproduce
## BetaHub Link
[View in BetaHub]()
Formatted Title:
[] -
Tag Combination:
beta-testing -priority
Best Practices for Mapping
Include Context:
- Add links back to BetaHub entries
- Include reporter information
- Reference game version and platform
Maintain Traceability:
- Use consistent formatting across tools
- Include unique identifiers
- Cross-reference related items
Optimize for Workflow:
- Map to appropriate priority levels
- Use relevant categories and labels
- Set up automatic assignments
Using Integrations
Sending Individual Items
From List View:
- Navigate to Bugs, Suggestions, or Tickets list
- Click the three-dots menu (…) next to the entry
- Select Send to…
- Choose your configured integration
From Detail View:
- Open the entry details page
- Click the three-dots menu (…) in the top-right corner
- Select Send to…
- Choose your configured integration
Bulk Operations
Multi-Select Sending:
- Use checkboxes to select multiple entries
- Click bulk actions menu
- Choose Send to… for selected items
- Select target integration
Entry Linking and Updates
Automatic Linking:
- BetaHub creates bidirectional links between entries
- External item IDs are stored for reference
- Status sync (where supported by external tool)
Update Behavior:
- Subsequent “Send to…” actions update existing items
- No duplicate creation in external systems
- Manual trigger required (no automatic sync)
Changes made in external systems are not automatically reflected back in BetaHub. Integration is currently one-way from BetaHub to external systems.
Advanced Configuration
Custom Field Mapping
Jira Custom Fields:
{
"customfield_10001": "",
"customfield_10002": "",
"customfield_10003": "BetaHub Import"
}
GitHub Issue Templates:
---
title:
labels: , bug
assignees:
---
**Bug Report from BetaHub**
**Steps to Reproduce:**
**Environment:**
- Game Version:
- Platform:
- Device:
[View in BetaHub]()
Conditional Logic
Priority-Based Assignment:
assignee: developer-team
Tag-Based Routing:
Webhook Configuration
Outgoing Webhooks:
- Real-time notifications to external services
- Custom payload formatting
- Retry logic for failed deliveries
- Security headers and authentication
Example Webhook Payload:
{
"event": "bug_created",
"project": "",
"bug": {
"id": "",
"title": "",
"priority": "",
"url": ""
},
"timestamp": ""
}
Integration Monitoring
Success Tracking
Integration Dashboard:
- Success/failure rates for each integration
- Recent sync activity logs
- Error message analysis
- Performance metrics
Audit Trail:
- Track which items were sent where
- Monitor user actions and timestamps
- Maintain compliance records
Error Handling
Common Error Types:
- Authentication failures
- Network connectivity issues
- Field validation errors
- Rate limiting responses
Resolution Strategies:
- Automatic retry with exponential backoff
- User notification for manual intervention
- Fallback to alternative integrations
- Error log aggregation for analysis
Troubleshooting
Authentication Issues
Token Expiration:
- Check token validity in external system
- Regenerate tokens as needed
- Update BetaHub configuration
Permission Problems:
- Verify account permissions in target system
- Check project-specific access rights
- Confirm API scope and capabilities
Field Mapping Errors
Validation Failures:
- Review required fields in target system
- Check data format requirements
- Test with minimal field mappings
Template Syntax Errors:
- Validate dynamic expression syntax
- Test templates with sample data
- Check for missing or invalid variables
Performance Issues
Slow Sync Times:
- Review network connectivity
- Check external system status
- Optimize field mapping complexity
Rate Limiting:
- Implement request throttling
- Spread sync operations over time
- Contact external service for rate increases
Security Considerations
Credential Management
Best Practices:
- Use dedicated service accounts
- Rotate credentials regularly
- Apply principle of least privilege
- Monitor access logs
Token Security:
- Store tokens securely
- Never expose in logs or UI
- Use encrypted storage
- Implement token rotation
Data Privacy
Information Transfer:
- Review what data is sent to external systems
- Ensure compliance with privacy regulations
- Implement data retention policies
- Document data flows
Getting Help
Support Resources
Documentation:
- Platform-specific integration guides
- API reference documentation
- Field mapping examples
Community Support:
- Join our Discord server
- Community knowledge base
- User-contributed examples
Direct Support:
- Technical support for complex integrations
- Custom integration development
- Enterprise integration consulting
Common Questions
Q: Can I sync data back from external tools to BetaHub? A: Currently, integration is one-way from BetaHub to external systems. Bidirectional sync is planned for future releases.
Q: How often does synchronization occur? A: Sync is manual and triggered by user action. Automatic sync is not currently supported.
Q: Can I integrate with multiple tools simultaneously? A: Yes, you can configure multiple integrations and choose which tool to send each item to.
Next Steps
- Game Engine Integration - In-game bug reporting setup
- API Access - Custom integration development
- Advanced Features - Explore AI-powered capabilities