| Project | A project is pre-configured with issue types, a workflow, screens and fields |
| Board | The central tool for working with issues. A board is created for every project. |
| Dashboard | For example to show «issues assigned to me» |
| Issue | …, issue types might be: Bug, Change Request, Story etc. |
| Component | used to group issues. |
| Workflow | defines the states (such as Open, In Progress etc) and edges between them through which an issue travels |
| Field | |
| Initiatives | A collection of epics |
| Screen | a collection of fields that is displayed at a time |
| Label | |
Issue types
Depending on the applications, there are different default issue types.
Jira Core
| Task | Work that needs to be done |
| Substask | A task is finished when its subtasks are finished |
Jira Software
| Epic | Typically the one parent issue type for a software project |
| Bug | |
| Task | |
| Subtask | |
| Story | aka «User story»: a short requirement or request, written from the perspective of a user. The smallest definable unit of work. |
Jira Service Management
| Change | |
| IT help | |
| Incident | |
| New feature | |
| Problem | |
| Service request | |
| Service request with approval | |
| Support | |