Jira tracks the work well. What it doesn’t keep is a page per feature that’s still right once the tickets close. The Jira plugin brings your board into Eidos, issues as tasks beside their specs, and sends your changes back one ticket at a time.
Free for macOS, Windows, and Linux. No account, no subscription.
Sound familiar?
The work moves in Jira. The description of what you’re building lives elsewhere, and falls behind as soon as delivery starts.
The feature was described in the epic, and the epic closed with the release. Six months later, finding what was agreed means digging through done tickets.
The requirements are in a wiki page and in the tickets, and they stopped agreeing in sprint two. Each person trusts a different one.
Coding agents read the ticket’s description. Why the feature exists, and what it won’t do, never reach them.
How it fits
With the software framework, every feature gets one spec, a markdown page in your project. The Jira plugin connects a board, and each issue arrives as a task linked to its spec. Close the ticket and the spec stays as the record.
What you will use most
Issues land as tasks beside the specs they serve. The Backlog can adopt Jira’s statuses, priorities, and issue types in one step, so the board looks the way your team knows it.
Comments on an issue become a thread on its task, so the conversation sits next to the spec, not in a second tab.
Ask the AI Agent to propose how your board’s statuses, types, and fields map to the Backlog. You accept or change each line.
Each spec has a history and a diff, so a change made after the tickets has a name and a date.
Back to Jira
Change a task in Eidos and send it back to its issue when you’re ready, or turn on auto sync to send it after a save or a push. Nothing syncs both ways on its own, so the board holds no surprises.
Set it up
Install the plugin, allow it, and sign in to your Jira site with your own Atlassian API token. Then pick a board you can see, and pull. Requests go straight from your computer to your Jira site, and your token stays on your machine, never in the project.
$ eidos plugin install @iUngerTime/jira
$ eidos plugin allow jira
$ eidos jira login your-team.atlassian.net
✓ signed in as [email protected]
$ eidos jira boardsStart here
Specs for the features and overview pages for the product, with Out of Scope in every template. Pick it in the app for a new project, then turn on the Backlog under Built-in plugins and install the Jira plugin.
An app, a service, or a system
Frames for architecture, audience, criteria, and market, and specs grouped by domain.
$ eidos install @BuildableWorks/softwareIn the app: New Project, then pick it from the list.
Download Eidos MD, install the software framework and the Jira plugin, and pull your team’s board today.
Free for macOS, Windows, and Linux. Your files stay plain text in a folder you own.