JiraOps

JiraOps is a VS Code extension for Jira operations. The current MVP finds supported remote web links attached to a Jira issue and displays them inside a focused Activity Bar webview.

✨ Features

• One-input Jira lookup: paste an issue key or browse URL and fetch linked operational resources.
• Explicit Jira connection control: connect, reuse, refresh, or disconnect Jira OAuth access on purpose.
• Focused VS Code experience: review remote links in a clean Activity Bar webview and open them externally.
• Safe, testable foundation: validate webview messages, parse Jira responses with Zod, and run deterministic E2E tests without real Jira credentials.

Current scope: remote web-link discovery only. Issue creation, comments, transitions, JQL search, and sprint workflows are not implemented yet.

🚀 Quick Start

Requirements:

• VS Code ^1.90.0
• Node.js >=20
• npm
• Jira Cloud account and Atlassian OAuth app for real lookups

Install and build:

npm install
npm --prefix e2e install
npm run build

Launch an extension development host:

code --extensionDevelopmentPath="$(pwd)"

Then open JiraOps in the Activity Bar, select Connect Jira, enter an issue key or browse URL, and select Fetch.

🔐 Jira Authentication

JiraOps uses jira-oauth-client. You can set these environment variables before the first real connection:

export JIRA_CLIENT_ID="your-atlassian-oauth-client-id"
export JIRA_CLIENT_SECRET="your-atlassian-oauth-client-secret"

If those variables are not available to VS Code, Connect Jira asks for the OAuth app client ID and client secret, then saves them in VS Code SecretStorage (system keychain). Environment variables still take priority over saved values.

Your Atlassian OAuth app must allow:

http://localhost:30129/callback

Use Connect Jira to start the browser OAuth flow. Fetch requires an existing connection and refreshes expired tokens when a refresh token is available. Use JiraOps: Clear Saved Jira OAuth Credentials from the Command Palette to remove saved OAuth app credentials.

Never log, commit, or share OAuth secrets, access tokens, refresh tokens, Authorization headers, or raw credential payloads.

🧪 Development

Prototype review:

python3 -m http.server 4174 --bind 127.0.0.1 --directory docs/designs/prototypes

Open http://127.0.0.1:4174/index.html.

🧭 Architecture

VS Code Activity Bar
  -> jiraOps.linksView webview
  -> jira-ops.js posts jiraOps.connectJira, jiraOps.disconnectJira, or jiraOps.fetchLinks
  -> JiraOpsPanelProvider validates the message
  -> parseIssueInput normalizes the issue key
  -> OAuthJiraTokenProvider connects, disconnects, resolves, or refreshes Jira tokens
  -> fetchJiraRemoteLinks calls Atlassian REST API
  -> parseRemoteLinksResponse maps safe display rows
  -> webview renders loading, success, empty, or error state

🛠 Troubleshooting

🗺 Roadmap

• Better authentication error states.
• Jira site selection for accounts with multiple cloud sites.
• More Jira issue operations after remote-link discovery is stable.
• Marketplace polish with PNG icon and screenshots.

📄 License

MIT

Made with ❤️ to make Jira work easier.