Current Case:
Currently If you create any issue created in GitHub you need to come and mannualy create a new issue in Hive.
Expected Case:
- Ask access to GitHub Account.
- Allow users to map hive projects with GitHub Projects
- If there are any new issues or comment in GithHub issue replicate the same in hive.
- You can Also store the GitHub Issue No in Hive as well as paste the hive issue no in GitHub.
Steps to follow
- Authentication
- Use GitHub OAuth
- Store access token and permissions
- Support multiple accounts and org-level access
- Project Mapping
- Map Hive Project ↔ GitHub Repo/Project
- Support many-to-one mapping
- One hive project many GitHub repo
- Real-Time Sync
- Use GitHub Webhooks
- Trigger on issue create/update, comments, close/reopen
- Bi-directional Sync
- GitHub ↔ Hive issues
- Comments sync
- Status sync
- Unique Linking System
- Store GitHub Issue ID, URL, repo
- Add backlink comment in GitHub to Hive
- Attachments & Media Sync
- Sync images, files, links
- User Mapping
- Map GitHub users to Hive users
- Maintain proper assignment
- Activity Timeline
- Unified timeline showing GitHub + Hive activity
- Retry & Failure Queue
- Handle webhook failures
- Add logging dashboard
Current Case:
Currently If you create any issue created in GitHub you need to come and mannualy create a new issue in Hive.
Expected Case:
Steps to follow