Development tools for workflow control
Workvane builds Winds: focused tools that connect source code, tickets, and release state where engineering decisions already happen.
The first Wind is a Chrome extension for Jira + GitHub. More source and ticketing pairs can follow the same model.
Product family
Workvane is the product family. Winds are the tools that bring workflow state into the places developers already work.
Available now
A Chrome extension that puts Jira status, ticket recovery, and workflow actions directly inside GitHub pull requests.
See it in action
A short walkthrough: Free Jira status and assignee chips, then the Pro flow — ticket suggestions for keyless PRs, one-click transitions, and merge-blocker flags, all without leaving GitHub.
Recorded against a live GitHub pull-request list.
Jira + GitHub features
This first Wind starts from the PR page because that is where developers decide what is ready, blocked, stale, or missing a ticket.
Show ticket status and assignee chips next to every linked pull request.
Move Jira tickets through any workflow state without leaving GitHub. Configure conditions per transition so buttons only appear when the PR is actually ready.
Pro searches Jira and suggests the most likely ticket when a PR title or branch has no key. Pick one to associate the PR and write a remote link back to Jira.
Define statuses, aliases, chip colors, and row background signals per workflow — and make the gaps obvious: approved PRs with passing checks stand out when Jira is still behind.
Dry-run any configured transition against a real ticket from the dashboard. See which conditions pass or fail so you know exactly why a button does or doesn't appear.
Pro flags every PR row that has merge conflicts or unresolved review comments, so the PRs that look ready but actually can't ship stop being invisible in the list.
Pro adds an "Approve + create follow-up Jira ticket" option to GitHub's review form. After approving, a side drawer opens to file the follow-up ticket — project, issue type, title, description, labels — pre-linked to both the PR and the ticket the PR was working on.
Workvane is early and shaped by the people using it. Tell us which workflow friction to kill next — your request could be the next card on this page.
Request a feature →Getting started
Add your Jira domain, email, token, project keys, and status color rules.
Workvane reads ticket keys from titles, branches, local overrides, and suggestions.
Filter by Jira state, transition tickets, and link PRs back to Jira when needed.
Plans
Start with the free extension, then upgrade when you need workflow actions and ticket recovery.
For seeing Jira state where you already work.
For teams and solo devs who move tickets from GitHub.
Billed monthly. Switch to annual to save 20%.
Get Pro — MonthlyTeam billing and shared workflow presets are available for early customers.
Shape the product
The extension popup opens this feedback path. Early requests should shape the first public Chrome Web Store release.