Workvane brings Jira into the place you already work: GitHub pull requests. See ticket status and assignee on every PR row, filter the list by Jira state, and move tickets through your workflow with one click without leaving GitHub. Pro adds conditional transitions, ticket suggestions for keyless PRs, merge-blocker flags, and approve-with-follow-up-ticket. Your Jira token stays in your browser.
Hey PH π I'm Leo. I built Workvane because my GitHub PR list never told me the truth: which PRs were really ready, what Jira state each ticket was in, or which "ready" PRs were secretly blocked by conflicts or unresolved comments. I was living in two tabs and reconciling them in my head.
Workvane puts Jira status, assignee, filters, and one-click workflow transitions right on the GitHub PR page with per-transition conditions so a button only appears when the PR is genuinely ready. It's a Chrome extension; your Jira credentials stay in your browser (nothing hits our servers).
Free gives you the visibility (badges, chips, filters). Pro (48/yr) gives you the workflow control. It's early and shaped by users, tell me the workflow friction you want killed next π
Report
Keeping Jira and GitHub aligned has frustrated teams for years. Which workflow ends up saving developers the most time once they start using Workvane?
Report
Love that this lives right in the PR list, the keyless ticket suggestions sound especially useful. One thing that would seal the deal for our team is being able to see the PR's review status directly on the Jira ticket side, so the two views feel fully synced instead of one-directional.
Report
The token staying in the browser is a nice touch for security. One thing that would make this even better for our team: a way to link multiple Jira tickets to a single PR, since we often have one PR that closes out a parent epic plus a couple of subtasks. Right now it looks like the workflow assumes one ticket per PR.
Report
The merge-blocker flag is a smart touch, keeps quality gates visible without forcing a context switch. Nice work keeping the token client-side too.
Report
the fact that the jira token just sits in your browser and never hits a server is honestly such a thoughtful call, especially for something sitting on top of github all day
Report
No reviews yetBe the first to leave a review for Workvane β Jira + GitHub Wind
Keeping Jira and GitHub aligned has frustrated teams for years. Which workflow ends up saving developers the most time once they start using Workvane?
Love that this lives right in the PR list, the keyless ticket suggestions sound especially useful. One thing that would seal the deal for our team is being able to see the PR's review status directly on the Jira ticket side, so the two views feel fully synced instead of one-directional.
The token staying in the browser is a nice touch for security. One thing that would make this even better for our team: a way to link multiple Jira tickets to a single PR, since we often have one PR that closes out a parent epic plus a couple of subtasks. Right now it looks like the workflow assumes one ticket per PR.
The merge-blocker flag is a smart touch, keeps quality gates visible without forcing a context switch. Nice work keeping the token client-side too.
the fact that the jira token just sits in your browser and never hits a server is honestly such a thoughtful call, especially for something sitting on top of github all day