Jira launched in 2002 as a bug tracker. Twenty-plus years and many acquisitions later, it's the reigning standard for software work-tracking in mid-sized and large organizations. Loved or loathed depending on how it's been configured locally — Jira's biggest feature and biggest weakness are the same thing: you can configure almost anything.
← Back to Cross-Cutting Tools| Term | Meaning |
|---|---|
| Project | A container for issues with its own settings, board, and permissions. |
| Issue | A unit of work — Story, Task, Bug, Epic, Sub-task, or a custom type. |
| Epic | Big-picture work that contains many stories. |
| Sprint | A timebox of selected issues. Scrum boards organize around it. |
| Workflow | The state machine an issue moves through (To Do → In Progress → Done, plus your variants). |
| JQL | Jira Query Language — SQL-like filter syntax. Once learned, indispensable. |
| Component / Label | Lightweight categorization beyond project boundaries. |
| Confluence link | Inline embedding of pages, designs, decisions. |