Show Jira Cloud state, workflow actions, and ticket suggestions inside GitHub pull requests.
Users
8
+3 in 30 days
Rating
0.0 / 5
unchanged in 30 days
Ratings
0
0 in 30 days
Store rank
#215K
#180K among extensions
Version
1.2.0
updated 2 Oct 2026
Users
monthly, 4 months
Latest, 16 Oct 2026:8 usersMove the mouse over the chart for any month
Ratings count
monthly, 4 months
Latest, 16 Oct 2026:0 ratingsMove the mouse over the chart for any month
The Chrome Web Store rounds user counts down to the leading digit, so the user line moves in steps. The ratings count is exact and is the better signal of real adoption.
About Workvane: Jira + GitHub Wind
Workvane is a Chrome extension that brings Jira status, Jira workflow actions, and ticket-recovery tools directly into GitHub pull-request pages. Developers decide what is ready, blocked, stale, or missing a ticket on the PR page — so that is where Workvane puts the workflow truth, instead of forcing a context switch to Jira.
"Wind" is the name for each focused source-and-ticketing integration. Jira + GitHub is the first; Linear + GitHub, Jira + GitLab, and others follow the same model.
Key features:
- Jira badges in GitHub: ticket status and assignee chips next to every linked PR.
- One-click transitions: move Jira tickets through any workflow state without leaving GitHub, with per-transition conditions so buttons appear only when a PR is genuinely ready.
- Ticket suggestions: for a PR with no ticket key, Workvane searches Jira, suggests the most likely ticket, and links it (with a remote link back to Jira).
- Status styling & mismatch highlights: custom statuses, aliases, chip colors, and row signals; approved-and-passing PRs stand out when Jira is still behind.
- Transition diagnostics: dry-run any configured transition against a real ticket to see exactly why a button does or doesn't appear.
- Merge blockers at a glance: flags PR rows with merge conflicts or unresolved review threads.
- Approve with a follow-up ticket: approve a PR and file a follow-up Jira ticket, pre-linked to the PR and its original ticket, in one step.
Benefits:
- Stop context-switching between GitHub and Jira to read or update workflow state.
- Catch PRs that look ready but can't ship (conflicts, unresolved threads, stale Jira state).
- Keep Jira accurate without manual bookkeeping — including PRs that never had a ticket key.
- Configure once; conditions keep the PR list honest as the team works.