Introduction to Jira work items: Types, hierarchy, and fields

By Baylee Robards, Atlassian Product Marketing Manager, Jira
Key takeaways
Work item types distinguish kinds of work, including tasks, stories, and bugs.
Jira’s built-in hierarchy places epics above standard work items and subtasks below them.
Parent and child describe relative positions in the hierarchy rather than separate work item types.
Work item links express named relationships such as blocks, duplicates, and relates to without changing the hierarchy.
Depending on how your team uses Jira, a work item could represent a product task, a help desk ticket, a leave request, and more. You can update a work item as work progresses, adding details like the assignee, a description, or attachments, so everyone has the context they need in one place.
What are Jira work items?
A Jira work item is a single unit of work your team tracks in Jira, such as a task, story, bug, or epic. Work items were formerly called issues, and each one shows what needs to be done, who owns it, and where it stands.
Every work item has a work type, a status that moves through your workflow, and fields for details like priority and due date. Parent-child relationships and links connect work items, so teams can see how small tasks roll up to larger initiatives.
You can assign work items to teammates or AI agents, and Jira tracks every update in one place.
Meet the redesigned Jira work item view
Try the redesigned Jira work item view in beta. Key info is up front, tasks take fewer clicks, and your automations and integrations stay the same. Learn more about the new view here.
Are Jira work items and issues the same thing?
Yes. Atlassian renamed issues to work items in 2025 to evolve with the updated language across tools. The functionality is unchanged. Now the feature name better reflects the full range of work and workflows that various types of teams manage in Jira.
What are work types in Jira?
Work types let you identify, categorize, and distinguish between different kinds of work. Every Jira product comes with a set of default work types.
Jira admins can create and customize work types to match how your team works.
Work type | What it represents | Example |
Epic | A large body of work, often made up of several work items | Start a lemonade stand |
Story | A feature or requirement described from the user's point of view | Let customers pay by card |
Task | A piece of work that needs to be done | Buy cups and lemons |
Bug | A problem or error that needs to be fixed | Cash drawer won't open |
Subtask | A smaller, more granular part of a standard work item | Squeeze the lemons |
A subtask can be created for any standard work type and is added after a work item already exists. If you need more details, learn how to create and customize work types here.
How does the Jira work item hierarchy work?
Jira's default work item hierarchy has three levels: Epic at the top, then standard work items (story, task, bug), and subtasks at the bottom. Premium and Enterprise editions let you add levels above Epic.
Think of it like an organization. At the top you have leadership setting broad direction, supported by teams who carry out the detailed work. In the same way, Jira's hierarchy shows how small pieces of work ladder up to bigger goals:
Epics: Broad objectives, initiatives, or large bodies of work that break down into stories, tasks, and bugs.
Standard work types (story, task, bug): The work that gets done in support of those larger goals.
Subtasks: The smaller chunks a standard work type is broken into.
Parent and child describe the relationship between levels. Any work type can be both a parent and a child, with one exception: a subtask can only ever be a child, because nothing sits below it in the hierarchy.
What are fields on a work item?
A field is where a work item stores a specific piece of information, such as the assignee, due date, or status. Together, fields capture everything your team needs to know about a piece of work.
Jira includes default system fields, and you can create a custom field to collect information the defaults do not cover. Choosing which fields appear, which matter most, and where they sit helps your team move work forward faster.
The work item view is designed for flexibility in where you place fields. Its layout has five key regions, starting with the description, the first place people look when they open a work item.
How do you link related work items?
Linking connects work items that depend on or relate to one another, so dependencies stay visible across your team. As with any project, there may be dependencies between your tasks, and links make those relationships easy to see.
Out-of-the-box link types include relationships like blocks, is blocked by, relates to, duplicates, and clones. Every linked work item appears on each of the work items it connects, so the relationship is visible from either side.
Get started with Jira work items
Work items give every piece of work in Jira a clear owner, status, and place in the bigger plan. Start with the default work types, then add custom fields and links as your team's needs grow.
When you're ready, create your first work item, connect it to an epic, and link any dependencies. Your team will have the context it needs in one place, from first draft to done.
Jira work items: Frequently asked questions
Can you change a work item's type after it's created?
How do you find specific work items in Jira?
Can you update multiple work items at once?
Can AI create work items in Jira?
Recommended for you
Guide to Jira Plans
Build roadmaps, plan across teams, map dependencies, and balance capacity in one view with Jira Plans.
Guide to Jira workflows
Learn how to design workflows with statuses, rules, and AI agents that move work from creation to done in Jira.
Guide to Jira Boards
Visualize work, spot bottlenecks, and keep every sprint moving with Scrum and Kanban boards in Jira.