Documentation
SPIREX documentation
How every SPIREX feature actually works, written for the people using it, not a marketing summary. Each page documents the mechanics in detail and answers the questions people actually ask about it.
In short: SPIREX is a free, open-source alternative to Jira, and the 7 pages below document how each part of it works โ sprint boards and backlog planning, custom workflows and epics, time tracking and reporting, the Jira importer, AI ticket drafting, the REST API, and the role model. All of it is readable without an account, and where a feature has a limitation the page says so instead of describing an aspirational version.
Documentation by feature
Sprint boards
How sprint boards, backlog grooming and carry-over actually work in SPIREX: setting up a sprint, working the board, and closing it without losing work.01Workflows & epics
How the work hierarchy, the visual workflow editor, issue linking and the rich TipTap editor work in SPIREX, with the six core statuses your columns map to.02Time tracking & reporting
How worklogs, the three report views and CSV export work in SPIREX, and why estimates are never blended with logged time in a report.03Jira import
The mechanics of the SPIREX Jira importer: connecting Atlassian, what converts and what does not, epic-link resolution, and ghost users for unmatched people.04AI ticket drafting
How SPIREX drafts tickets from text, an image, a document or a live voice call, what model powers it, and what the free-tier AI-action quota means.05REST API
How SPIREX API keys, the X-Org-Id multi-tenant model and role-scoped permissions work, and what the REST API can read and write today.06Roles & permissions
How roles and permissions work in SPIREX: org-level roles, project-scoped access, admin and superadmin boundaries, and what each role can actually do.07
Which page answers which question
If you arrived with a specific question rather than a feature name, start here.
| Question | Page |
|---|---|
| How do I plan a sprint, groom the backlog, and carry unfinished work over? | Sprint boards |
| Can I define my own statuses, and how do epics and linked issues work? | Workflows & epics |
| How does time tracking work, and what do the reports actually count? | Time tracking & reporting |
| What exactly comes across when I import from Jira, and what does not? | Jira import |
| Can AI draft a ticket from a sentence, an image, or my voice? | AI ticket drafting |
| Is there a REST API, and how do scoped API keys limit what a key can do? | REST API |
| What can each role actually do, and who can change a project? | Roles & permissions |
Frequently asked questions
Yes. Every page here is public: no sign-up required to read how a feature works. Creating a workspace is only needed to actually use the feature.
Each page carries a visible "Published"/"Updated" date matching what actually shipped in the product at that time. Where a feature has a known limitation (kanban, for example), the docs say so rather than describing an aspirational version.
The public REST API page here covers authentication and permissions. The complete endpoint-by-endpoint reference lives in-app at /api-docs once you have an account and an API key, since it documents behaviour tied to a real key.
See it running on your own data
Reading how a feature works is one thing. A free workspace with a real Jira import is the fastest way to check whether it actually holds up.