Development tools for workflow control

Workvane

Workvane builds Winds: focused tools that connect source code, tickets, and release state where engineering decisions already happen.

Explore first Wind Install beta

The first Wind is a Chrome extension for Jira + GitHub. More source and ticketing pairs can follow the same model.

Workvane Free tier injecting Jira status and assignee chips into the GitHub pull request list
Free: Jira visibility in GitHub PR lists
Workvane Pro suggesting Jira tickets on a GitHub pull request without a Jira key
Pro: ticket suggestions for keyless PRs
Workvane Pro showing a completed Jira transition action on a GitHub pull request
Pro: Jira transitions from the PR page

Product family

One focused tool per source and ticketing pair.

Workvane is the product family. Winds are the tools that bring workflow state into the places developers already work.

Jira + GitHubBeta
Linear + GitHubSoon
Jira + GitLabSoon
Plane + GitLabSoon

Available now

Jira + GitHub Wind

A Chrome extension that puts Jira status, ticket recovery, and workflow actions directly inside GitHub pull requests.

Install beta See features
Live GitHub PR-list canary
Bulletproof against GitHub UI changes
Free and Pro flows verified
Transition diagnostics included

Jira + GitHub features

Make the PR list tell the whole workflow truth.

This first Wind starts from the PR page because that is where developers decide what is ready, blocked, stale, or missing a ticket.

01

Jira badges in GitHub

Show ticket status and assignee chips next to every linked pull request.

02

One-click transitions

Move Jira tickets through any workflow state without leaving GitHub. Configure conditions per transition so buttons only appear when the PR is actually ready.

03

Ticket suggestions

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.

04

Status styling

Define statuses, aliases, chip colors, and row background signals per workflow.

05

Mismatch highlights

Approved PRs with passing checks stand out when Jira is still behind.

06

Transition diagnostics

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.

07

Merge blockers at a glance

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.

Getting started

Install, configure, keep moving.

1

Connect Jira locally

Add your Jira domain, email, token, project keys, and status color rules.

2

Open GitHub PRs

Workvane reads ticket keys from titles, branches, local overrides, and suggestions.

3

Act from GitHub

Filter by Jira state, transition tickets, and link PRs back to Jira when needed.

Plans

Free for visibility. Pro for workflow control.

Start with the free extension, then upgrade when you need workflow actions and ticket recovery.

Free

For seeing Jira state where you already work.

$0
Join beta
  • Jira status badges
  • Assignee chips
  • Jira filters in PR lists
  • Basic mismatch highlighting

Pro

For teams and solo devs who move tickets from GitHub.

TBD
Request Pro access
  • Unlimited conditional transition actions
  • Configurable status colors and aliases
  • Jira ticket suggestions for keyless PRs
  • PR association overrides and Jira remote links
  • Transition diagnostics and dry-run testing
  • Conflict and unresolved-comment flags in PR lists

Need Pro for a team?

Team billing and shared workflow presets are available for early customers.

Talk about team Pro

Shape the product

Suggest a Wind, workflow rule, or Pro feature.

The extension popup opens this feedback path. Early requests should shape the first public Chrome Web Store release.

Suggest a feature Contact Leo