Workvane: Jira + GitHub Wind
Show Jira Cloud state, workflow actions, and ticket suggestions inside GitHub pull requests.
As of June 2026, Workvane: Jira + GitHub Wind has — users in the Developer Tools category.
Usersno change0%
—
—
Ratingno change0%
—
— reviews
Reviewsno change0%
—
Version
1.0.0
Manifest V3
History
1 snapshotsTracking since Jun 24, 2026.
Not enough history yet for this metric — the chart fills in as we collect more snapshots.
View as table
| Date | Users | Rating | Reviews | Version |
|---|---|---|---|---|
| Jun 24, 2026 | — | — | — | 1.0.0 |
| Now | — | — | — | 1.0.0 |
Permissions & access
- Permissions
- storagetabsidentity
- Host access
- https://github.com/*, https://api.github.com/*
Screenshots
About
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.
Technical
- Version
- 1.0.0
- Manifest
- V3
- Size
- 234KiB
- Min Chrome
- 88
- Languages
- 1
- Featured
- No
Metadata
- ID
- gcnehphpcpfjjoggebljfnhmnfgmalja
- Developer ID
- u4d10c6df303147b18d671da168239ce4
- Developer Email
- [email protected]
- Created
- Jun 23, 2026
- Last Updated (Store)
- Jun 23, 2026
- Last Scraped
- Jun 24, 2026
- Website
- workvane.com
- Support URL
- —
- Privacy Policy
- https://workvane.com/privacy
Data sourced from the Chrome Web Store · last verified Jun 24, 2026.