Taskify already handles project management well — kanban, calendar, search, roles. One feature that would make it viable as a Jira replacement for development teams is bidirectional GitHub issue sync.
The idea: link a GitHub repository to a Taskify project, then have issues flow both ways — GitHub Issues appear as Taskify tasks, and Taskify task updates sync back to GitHub. This would let teams use Taskify as their project management layer while keeping development activity visible on GitHub.
Suggested scope for an MVP:
- OAuth-based GitHub repo connection per project
- One-way import on connect (pulls existing GitHub Issues as Taskify tasks, linked by GitHub issue ID)
- Webhook receiver that creates/updates Taskify tasks when GitHub issues change (opened, closed, assigned, labelled)
- Periodic background sync to catch missed webhook events
Why this fits Taskify: the stack already handles this well — Hono.js can serve webhook endpoints, Appwrite handles auth sessions and database, and the Next.js app router can handle the OAuth flow with GitHub.
I am happy to elaborate on the webhook payload schema or Appwrite data model changes needed if this direction is useful.
Taskify already handles project management well — kanban, calendar, search, roles. One feature that would make it viable as a Jira replacement for development teams is bidirectional GitHub issue sync.
The idea: link a GitHub repository to a Taskify project, then have issues flow both ways — GitHub Issues appear as Taskify tasks, and Taskify task updates sync back to GitHub. This would let teams use Taskify as their project management layer while keeping development activity visible on GitHub.
Suggested scope for an MVP:
Why this fits Taskify: the stack already handles this well — Hono.js can serve webhook endpoints, Appwrite handles auth sessions and database, and the Next.js app router can handle the OAuth flow with GitHub.
I am happy to elaborate on the webhook payload schema or Appwrite data model changes needed if this direction is useful.