Jiraffe 🦒
Jira inside VS Code: your issues, the full issue card, attachments, time logging (including Tempo), status changes, epics and releases. Works with several Jira instances at once — Server/Data Center and Cloud side by side.
It covers the daily routine, not all of Jira. Creating and editing issues is not there yet.
The UI follows the VS Code display language: English or Russian. Русская версия README
New in 0.8. “Open in Agentura ▾” on the issue card: with Agentura 0.9 the issue's AI chats are grouped under it — continue the latest or start a new one, and see the issue's changes beside the chat. Plus a public API for other extensions, now with writing (comment, transition, worklog). See AI chat and API for other extensions below.

Features
Issues. Assigned to me, by project, or any JQL. Quick filters by status category, type, priority and instance. Search by key (ABC-123) or text. Your saved filters and Jira favourite filters in a separate view.

Issue card. Description, comments, change history, work log, people, epic and fix versions. Clicking the status opens the transitions available to you; required fields with a list of values (resolution, etc.) are asked for in a picker.

Attachments. Image previews in the description, comments and attachments tab, with a lightbox. Download one or all, open text files in the editor. Files go to .jiraffe/<KEY>/ in the workspace (git-ignored automatically).

Time logging. From the card or the tree. Uses Tempo where it is installed (including work attributes), the standard Jira worklog otherwise. The status bar shows how much you've logged today against your workday.


Epics and releases. Per-project lists with progress. Releases can follow several projects at once: tick them in the project picker in the view title, the × on a project stops following it. An epic or release opens in a tab with a status breakdown and its issues. A release tab filters its issues without leaving the editor: click the progress tiles or the legend to pick a status category, search by key or summary, narrow by Status (the workflow statuses themselves), Assignee, Type, Priority and Epic (with counts), Only mine, group by assignee, epic or status; Copy JQL and Save as filter turn the current selection into JQL for the Filters tab.
AI chat. With the Agentura extension installed, the issue card has an “Open in Agentura ▾” button: the issue goes in as context and its link is typed into the input. If the issue already has chats, a menu offers to continue the latest one, pick another, or start a new chat.
API for other extensions. (await getExtension('fosteev.jiraffe').activate()) returns { apiVersion: 2, instances(), issue(instanceId, key), myself(instanceId), openIssue(instanceId, key, beside?), onDidChangeInstances, addComment(instanceId, key, body), transitions(instanceId, key), transition(instanceId, key, transitionId), logWork(instanceId, key, { seconds, started?, comment?, aiTokens? }) } (in an untrusted workspace Jiraffe does not activate, so there is no API). Limited to this workspace's instances; tokens and emails are never exposed. v2 adds writing as you (comment, transition, worklog): arguments are validated (comment up to 32,000 characters; a transition must be one of transitions() and have no required screen fields; worklog 1 s to 24 h, not in the future, Tempo with required attributes is refused; a retry right after a write that ended without a response is refused once, since it may have been saved), and there are no dialogs. Check apiVersion >= 2, not === 2: later versions only add methods. Note that any installed extension can call it and read and change your Jira issues with your connections (including comments that mention people) — as with any VS Code extension API, install only extensions you trust.
Find. ⌘F / Ctrl+F searches the text of an open issue, epic or release tab. In the sidebar views use VS Code's tree find: focus a view and press ⌥⌘F / Ctrl+Alt+F or just start typing — it looks through the loaded items only.


Supported Jira
| Type |
Auth |
| Server / Data Center 8.22+ |
Personal Access Token. A context path is fine: https://host/jira |
| Cloud |
Account email + API token |
Tokens are stored in VS Code SecretStorage, never in settings.json. The extension talks only to the Jira instances you add, and runs only in trusted workspaces.
Tempo is supported on Server/DC. On Cloud, time goes to the standard worklog.
Install
Requires VS Code 1.90+.
- Install Jiraffe from the VS Code Marketplace (Cursor, VSCodium: Open VSX). Or download
jiraffe-<version>.vsix from Releases, or build it: npm ci && npm run package.
- Command Palette → Extensions: Install from VSIX…, or
code --install-extension jiraffe-0.3.0.vsix.
- A giraffe icon appears in the Activity Bar.
Adding an instance
Command Palette → Jiraffe: Add Instance, or the button in an empty view. Enter the URL, type and token. You can paste an issue link instead of the URL — the base address is taken from it. The connection is checked right away; a failing instance is not saved.
Instances per workspace
Connections are shared across windows, but each workspace can show only some of them: the server icon in the Issues or Filters view title, or in .vscode/settings.json:
{ "jiraffe.instances": ["https://jira.example.com"] }
Mode, project, quick filters, the Epics project and the Releases projects are remembered per workspace too.
Settings
Open the Jiraffe Settings tab with the gear in the title of the Issues, Filters, Epics and Releases views or the Jiraffe: Open Settings command. It has sections for connections (status, token change, rename, disconnect, which instances this workspace uses), the issue list, attachments (with a hint and a button when the folder is not in .gitignore), time tracking and integrations. Changes apply at once and go to the same settings as below; every setting shows where it is stored, and a changed one has a Reset link. The integrations section has two switches for the public API used by other extensions: access at all, and writing on your behalf. Both are on by default and, being user-level settings, cannot be changed from a project's .vscode/settings.json. The switches cover the API object and the jiraffe.downloadAttachment command; Jiraffe's other commands work as before and change Jira only after you confirm.
| Setting |
Default |
|
jiraffe.instances |
all |
Instances shown in this workspace (URLs or ids) |
jiraffe.maxResults |
50 |
Page size for issue and epic lists |
jiraffe.attachmentsDir |
.jiraffe |
Where attachments are saved, relative to the first workspace folder |
jiraffe.maxImageMb |
5 |
Max image size for previews |
jiraffe.workdayHours |
8 |
Workday length for the "today" summary |
jiraffe.api.enabled |
on |
Let other extensions use Jiraffe's API (user settings only) |
jiraffe.api.allowWrites |
on |
Let them comment, change status and log work as you (user settings only) |
Not yet
Subtasks and linked issues, assigning, creating and editing issues, comments, weekly time summary, Tempo Cloud.
Development
npm ci
npm run watch # then F5 in VS Code
npm test
npm run lint
License
MIT