Jira to PR

A VS Code extension for moving safely from an assigned Jira ticket to a GitHub pull request.

Workflow

1. Open the repository or multi-root workspace you want to use. If VS Code has multiple Git repositories open, use Jira to PR: Select Repository or the repository control at the top of the dashboard. The selection is remembered for that workspace.
2. Run Jira to PR: Connect to Jira, then choose an API token or an Atlassian OAuth access token issued by your organization’s SSO/OAuth integration.
3. Click the Jira to PR briefcase icon in the Activity Bar to open the dashboard.
4. Select a ticket from the dashboard or Ticket List to read its title and description.
5. Select Create Branch…, edit the suggested name, and approve branch creation. The dashboard then exposes Rename and Delete controls for that ticket branch.
6. Select the general Work with AI… action, choose any detected installed assistant (for example Copilot, Gemini, Codex, Claude, or another coding assistant), and add optional extra context. GitHub Copilot Chat receives the Jira prompt directly. Codex opens a new sidebar chat and copies the prompt to the clipboard for you to paste once. Other assistants receive the prompt directly when their extension command supports it, with the clipboard retained as a fallback.
7. Select Complete, commit & push when implementation is finished. Review and approve the files, commit message, and push separately.
8. Select Review changes to inspect the exact pushed commit, then check I have reviewed (or use the button in the review view).
9. Select Raise pull request and approve the GitHub repository, branches, title, and description.

PR creation is disabled and independently blocked by the command until the exact pushed commit has been reviewed. New commits or uncommitted workspace changes invalidate the review gate.

Canceling any approval stops that action. Manually entered Jira and GitHub tokens are stored in VS Code SecretStorage rather than user or workspace settings. GitHub browser sign-in uses VS Code’s built-in GitHub authentication provider and does not duplicate its token in this extension.

Requirements

• VS Code 1.85 or newer
• Node.js 18 or newer for development
• Git with an origin remote
• Jira Cloud API token, or an Atlassian OAuth access token that grants access to the selected site and has Jira read scopes
• For PR creation, a github.com origin and either VS Code GitHub sign-in or a fine-grained GitHub token with Pull requests: write permission

The default base branch and branch prefix can be changed in VS Code settings:

{
  "jiraToPr.defaultBranch": "develop",
  "jiraToPr.branchPrefix": "feature"
}

Development

npm install
npm run typecheck
npm run lint
npm test
npm run build

Press F5 in VS Code to run an Extension Development Host for interactive Jira, Git, and GitHub testing. External API operations require real credentials and always remain behind the approval dialogs described above.

Manual deployment

Sign in once with npx vsce login Kayser, or set the VSCE_PAT environment variable. Then use the command matching the release type:

npm run deploy:patch  # 1.0.0 -> 1.0.1 (bug fixes)
npm run deploy:minor  # 1.0.0 -> 1.1.0 (new backward-compatible features)
npm run deploy:major  # 1.0.0 -> 2.0.0 (breaking changes)

Each command builds the extension, increments the version in package.json, publishes it to the VS Code Marketplace, and creates a Git commit and version tag.