| Issue | One unit of work: a feature, a bug, a task. Each has a readable key such as ABC-00042. |
| Project | A container for issues and documents. Projects can hold sub-projects. |
| Epic | An issue that groups related issues around a theme. Its progress is the progress of the issues under it. |
| Story, Task, Bug, Sub-task | The kinds of issue: something a user wants, work to be done, something broken, a small step inside one of these. |
| Status | Where an issue is now: Backlog, To do, In progress, Testing, In review, Done, Reopened. An organization can rename them. |
| Workflow | The rules for which status may follow which, and on what conditions. |
| Resolution | Why an issue is Done: Fixed, Won't fix, Duplicate, Cannot reproduce or Incomplete. |
| Section | A typed part of an issue, such as its pre-analysis, decisions or verification. |
| Definition of Done | A checklist an issue must satisfy before it is finished. |
| Backlog | Work not started yet. Different from unplanned, which is work in no sprint. |
| Inbox | A project's notes for requests nobody has decided on yet, later turned into issues or discarded. |
| Deadline | A dated fact from outside that may break something, such as a certificate expiry or a provider's change, with reminders before it falls due. |