Jira Context
Turn a Jira story into a local AI-ready context file for Cursor, Copilot, and other coding assistants.
Supported: Jira Cloud and Jira Server / Data Center — use your org’s Jira site URL.
What it does
- Connects to your org Jira site (Cloud or Server / Data Center)
- Fetches a story by key (for example
ABC-123)
- Writes a clean
.context/ABC-123.txt file you can give to an AI assistant
Setup (3 steps)
Step 1 — Install
Marketplace
- Open Extensions (
Cmd+Shift+X or Ctrl+Shift+X)
- Search for Jira Context
- Click Install
On first install, click Get Started when the welcome prompt appears.
Or run Jira Context: Welcome anytime from the Command Palette (Cmd+Shift+P / Ctrl+Shift+P).
From VSIX (optional)
- Command Palette → Extensions: Install from VSIX...
- Select
jira-context-*.vsix
- Reload the window if asked
Step 2 — Add Jira credentials
- Command Palette → Jira Context: Update Credentials
- Enter your org URL and login details:
| Field |
Jira Cloud |
Jira Server / Data Center |
| Base URL |
https://your-company.atlassian.net |
https://jira.company.com (add /jira if your org uses a context path) |
| Email / Username |
Atlassian account email |
Jira username (or email if your org uses it) |
| Token / Password |
API token |
Password or Personal Access Token (PAT) |
The extension detects Cloud vs Server from the URL automatically.
Do not paste issue links like /browse/ABC-123.
Credentials are saved in VS Code / Cursor Secret Storage only — not in project files.
Step 3 — Generate a context file
- Open a project folder in VS Code / Cursor (required)
- Command Palette → Jira Context: Generate Story Context
- Enter the issue key (example:
ABC-123)
- Wait for the file to open — usually at
.context/ABC-123.txt
- Attach or reference that file in Cursor / Copilot when you implement the story
Done.
Commands
| Command |
When to use it |
| Jira Context: Welcome |
Open the guided walkthrough |
| Jira Context: Update Credentials |
First setup, or when login fails |
| Jira Context: Generate Story Context |
Create / refresh a story context file |
Optional settings
Open Settings and search for Jira Context:
| Setting |
Default |
Meaning |
| Include Comments |
on |
Add Jira comments to the file |
| Context Folder |
.context |
Where files are written |
| Auto Open File |
on |
Open the file after generation |
| Overwrite Existing |
Ask |
Ask before replacing an existing file |
Troubleshooting
Commands do not appear
- Reload the window: Command Palette → Developer: Reload Window
- Search again for Jira Context (include the J)
- Confirm the extension is enabled in Extensions
Authentication failed (401)
Cloud
- Run Jira Context: Update Credentials
- Use your Atlassian email + a new API token
- Base URL must be
https://your-company.atlassian.net
Server / Data Center
- Confirm username (not always email)
- Try password, or a Personal Access Token if your admin enabled PATs
- Confirm Base URL includes any context path (example:
https://jira.company.com/jira)
Unable to reach Jira / network error
- Open the same Base URL in a browser
- Check VPN / proxy / firewall
- Confirm the URL host and port are correct for your org
Issue not found (404)
- Check the key format:
PROJECT-123 (not a URL)
- Open that issue in Jira with the same account
- Confirm project access
- On Server/DC, confirm the Base URL context path is correct
Access denied (403)
Your account can connect, but cannot view that issue. Ask for project access, or try another issue.
No workspace folder is open
Open a folder first (File → Open Folder), then run Generate Story Context again.
Context files are written inside the opened project.
File did not appear
- Look under
.context/ in the project root
- Check Settings → Context Folder
- Open View → Output → select Jira Context for details
Still stuck?
- View → Output → choose Jira Context
- Copy the latest error lines
- Re-run Update Credentials, then Generate Story Context
What the generated file contains
Example path: .context/ABC-123.txt
- Story metadata (key, summary, status, priority, type, people, labels, components, epic, links)
- Description
- Acceptance Criteria
- Comments (if enabled)
- AI implementation instructions
- Implementation checklist
Known limits
- One workspace folder is used for output (the first open folder)
- Some Server/DC auth setups (SSO-only, cert auth) may need a PAT or local password enabled by your admin
- Attachments, Confluence pages, and sprint boards are not fetched yet
Develop this extension locally
- Open this repo
npm install- Press F5
- In the new window, run Jira Context: Welcome
License
MIT
Repository
https://github.com/sharadbharsakal/Jira-Context
