Seamlessly connect your FeatureShark feature requests with GitHub Issues to create a unified development workflow from user feedback to code deployment.
The GitHub integration enables you to:
Before starting, ensure you have:
Map FeatureShark statuses to GitHub issue states:
Default Mapping:
FeatureShark Status → GitHub State
Under Review → Open (draft)
Planned → Open (ready for development)
In Development → Open (in progress)
Testing → Open (in review)
Released → Closed (completed)
On Hold → Open (blocked)
Declined → Closed (won't fix)
Custom Labels:
FeatureShark Priority → GitHub Labels
Critical → priority:critical, type:bug
High → priority:high, type:enhancement
Medium → priority:medium, type:feature
Low → priority:low, type:nice-to-have
Issues are created when feature requests reach certain milestones:
Default Triggers:
Custom Triggers:
Standard GitHub Issue Template:
# Feature Request: [Title from FeatureShark]
## Original Request
**Submitted by:** [User name/email]
**Votes:** [Current vote count]
**Category:** [FeatureShark category]
**Priority:** [Calculated priority level]
## Description
[Original user description from FeatureShark]
## User Stories
[AI-generated or manually added user stories]
## Business Impact
- **Vote Count:** [X] users want this feature
- **User Segments:** [Enterprise/Free/Power users]
- **Revenue Impact:** [Estimated ARR impact]
- **Support Reduction:** [Potential ticket reduction]
## Acceptance Criteria
- [ ] [Criterion 1 based on user request]
- [ ] [Criterion 2 from discussion]
- [ ] [Criterion 3 from business requirements]
## Technical Considerations
[Any technical notes from team discussion]
## Related Links
- **FeatureShark Request:** [Direct link]
- **User Discussion:** [Comments thread]
- **Related Requests:** [Similar feature links]
---
*This issue was automatically created from FeatureShark request #[ID]*
*Last synced: [Timestamp]*
When first setting up the integration:
Selective Migration:
Batch Processing:
Quality Control:
GitHub activities automatically update FeatureShark status:
Issue State Changes:
Development Activity:
FeatureShark changes reflected in GitHub:
Status Changes:
Community Activity:
Not all comments need to sync between platforms:
Sync to GitHub:
Keep in FeatureShark Only:
Sync to FeatureShark:
Connect code changes to feature requests:
PR Title Conventions:
feat: Add dark mode toggle (closes #FR-123)
fix: Mobile offline sync issues (#FR-456)
docs: Update API documentation for webhooks (#FR-789)
PR Description Templates:
## Changes
[Description of code changes]
## Feature Request
**FeatureShark Link:** [URL to original request]
**User Votes:** [Current vote count]
**Business Impact:** [Why this matters]
## Testing
- [ ] Unit tests added/updated
- [ ] Integration tests passing
- [ ] Manual testing completed
- [ ] User acceptance criteria met
## User Communication
- [ ] Release notes drafted
- [ ] User documentation updated
- [ ] Support team informed
- [ ] FeatureShark status updated
Multi-Request PRs: Handle pull requests that address multiple feature requests:
feat: Improve search functionality
Addresses multiple user requests:
- Advanced filtering (#FR-123, 89 votes)
- Search result sorting (#FR-124, 67 votes)
- Saved search queries (#FR-125, 45 votes)
Total user impact: 201 votes, 15+ enterprise requests
Partial Implementation: Track incremental progress on large features:
feat: Mobile offline mode - Phase 1
Implements basic offline functionality for #FR-456
- ✅ Local data storage
- ✅ Basic sync mechanism
- ⏳ Conflict resolution (Phase 2)
- ⏳ Advanced sync options (Phase 3)
Progress: 60% complete, on track for Q3 delivery
Generate user-facing release notes from GitHub data:
Release Note Generation:
# Release 2.4.0 - March 2024
## New Features 🚀
**Dark Mode Interface** - #FR-123 (127 votes)
Finally here! Toggle between light and dark themes in your account settings.
*Thanks to @sarah_designer and @mike_frontend for the beautiful implementation!*
**Bulk Data Export** - #FR-124 (89 votes)
Export your data in CSV, Excel, or JSON formats with custom filtering options.
*Requested by many of our enterprise customers - now available for all users!*
## Improvements ⚡
**Faster Search Results** - #FR-125 (67 votes)
Search results now load 3x faster with improved indexing.
**Mobile Performance** - #FR-126 (45 votes)
Reduced app size by 40% and improved loading times on mobile devices.
## Bug Fixes 🐛
- Fixed offline sync conflicts (#FR-127)
- Resolved notification delivery issues (#FR-128)
- Improved error handling for large file uploads (#FR-129)
---
**Total User Requests Addressed:** 5 features, 373 total votes
**Release Highlights:** [Link to detailed release notes]
Automatically notify users when their requested features ship:
Individual Notifications:
🎉 Your requested feature is now live!
Hi Sarah,
Great news! The "Dark Mode Interface" feature you voted for
has been released in version 2.4.0.
Your Impact:
- You were voter #23 of 127 total votes
- This feature was our #2 most requested improvement
- Development time: 6 weeks from approval to release
Try It Now: [Direct link to new feature]
What's Next: Check out our roadmap for upcoming features
Thanks for helping shape our product!
The FeatureShark Team
Digest Notifications:
📦 March Feature Releases - 5 of Your Voted Features Shipped!
This month we released several features you voted for:
🌙 Dark Mode Interface (you voted ✓)
📊 Bulk Data Export (you voted ✓)
⚡ Faster Search (you voted ✓)
📱 Mobile Performance (you voted ✓)
🔧 Better Error Handling (you voted ✓)
Your engagement helps us prioritize development. Keep the
great feedback coming!
[View Full Release Notes] [See Current Roadmap]
Track feature request to deployment pipeline:
Key Metrics:
Sample Report:
Feature Development Cycle Time Report
Q1 2024 (Jan-Mar)
Average Cycle Times:
📋 Request → Planned: 12.3 days (↓ 2.1 days from Q4)
⚡ Planned → Development: 8.7 days (↑ 1.2 days from Q4)
🧪 Development → Testing: 18.4 days (↓ 4.3 days from Q4)
🚀 Testing → Release: 5.2 days (↓ 0.8 days from Q4)
Total Average: 44.6 days (↓ 5.4 days from Q4)
Fastest Feature: Mobile dark mode (28 days total)
Slowest Feature: Advanced analytics (73 days total)
Bottlenecks Identified:
1. Planning phase delays for complex features
2. Testing resource constraints in March
3. Release coordination for breaking changes
User Satisfaction Post-Release:
Feature Release Satisfaction Report
March 2024 Releases
Overall Satisfaction: 4.6/5 (↑ 0.3 from Feb)
By Feature:
🌙 Dark Mode: 4.8/5 (127 responses)
📊 Data Export: 4.5/5 (89 responses)
⚡ Search Speed: 4.7/5 (67 responses)
📱 Mobile Perf: 4.4/5 (45 responses)
Common Feedback Themes:
✅ "Exactly what we needed"
✅ "Works better than expected"
⚠️ "Minor UI polish needed"
⚠️ "Documentation could be clearer"
Action Items:
- UI improvements for data export (scheduled for 2.4.1)
- Enhanced documentation (in progress)
- Follow-up user research for mobile performance
Track integration reliability and performance:
Daily Health Check:
GitHub Integration Status
March 22, 2024
Sync Performance:
✅ Status Updates: 98.7% success rate (47/48 attempts)
✅ Comment Sync: 94.2% success rate (245/260 attempts)
✅ Issue Creation: 100% success rate (12/12 attempts)
⚠️ PR Linking: 89.3% success rate (25/28 attempts)
Recent Issues:
- 3 comment sync failures (GitHub API rate limits)
- 3 PR linking failures (malformed commit messages)
Automatic Retries: 5 successful, 1 pending
Manual Intervention Needed: 1 item (investigated)
Overall Integration Health: 96.8% ✅
Problem: Status updates not syncing from GitHub to FeatureShark Diagnostic Steps:
Solutions:
Problem: GitHub issues not being created for approved requests Diagnostic Steps:
Solutions:
For Active Development Teams:
For Large Feature Request Volumes:
Automate additional workflows with GitHub Actions:
Auto-Testing on Feature Completion:
name: Feature Request Validation
on:
issues:
types: [closed]
jobs:
notify-featureshark:
if: contains(github.event.issue.body, 'FeatureShark')
runs-on: ubuntu-latest
steps:
- name: Extract FeatureShark ID
id: extract
run: echo "::set-output name=request_id::$(echo '${{ github.event.issue.body }}' | grep -o 'FR-[0-9]*')"
- name: Trigger User Testing
run: |
curl -X POST "${{ secrets.FEATURESHARK_WEBHOOK_URL }}" \
-H "Content-Type: application/json" \
-d '{"request_id": "${{ steps.extract.outputs.request_id }}", "action": "start_user_testing"}'
Automatic Documentation Updates:
name: Update Feature Documentation
on:
pull_request:
types: [merged]
jobs:
update-docs:
if: contains(github.event.pull_request.body, 'FR-')
runs-on: ubuntu-latest
steps:
- name: Update User Documentation
run: |
# Extract feature request details
# Generate documentation updates
# Commit to docs repository
# Notify FeatureShark of documentation update
Handle complex projects with multiple repositories:
Repository Routing Rules:
{
"routing_rules": [
{
"category": "Mobile App",
"repository": "company/mobile-app",
"labels": ["mobile", "ios", "android"]
},
{
"category": "API",
"repository": "company/api-server",
"labels": ["api", "backend", "integration"]
},
{
"category": "Web App",
"repository": "company/web-client",
"labels": ["frontend", "web", "ui"]
}
]
}
Continue building your integration ecosystem:
Setup Time: 20-30 minutes
Maintenance: 5-10 minutes per week
Last Updated: September 2025
Still need help? Contact our support team