Learn how to set up Jira Software Cloud and integrate it with other products and applications.
Learn how to configure your Jira Software Cloud company-managed projects to suit your agile development processes.
Learn how to create, search, and work with issues in software projects, manage your profile, and more.
Learn how to get started, enable features, and manage and administer team-managed projects.
Plan and view work across multiple teams, projects, and releases with Advanced Roadmaps.
A guide on how to deploy and monitor an application built on AWS using Atlassian and third-party tools.
This page is for team-managed projects
If the lower-left of your project sidebar says you're in a company-managed project, check out these company-managed project articles instead.
Learn more about the difference between company-managed and team-managed projects.
In Jira, an issue can have subtasks that can be assigned and tracked individually. This allows you to break down the work in your project to smaller, more manageable pieces.
Add a subtask issue type
Subtask issue types are different from regular issue types. By default, team-managed projects have subtask issue types enabled. If your project doesn’t have the subtask issue type, you’ll need to add it:
Navigate to your team-managed software project.
Go to Project Settings > Issue types.
Select Add issue type.
You can create subtasks under any standard issues, like stories, bugs, or tasks. Note that you cannot create subtasks under epics or other subtasks.
When viewing an issue
On the board or backlog, select an issue.
Select Add a child issue
Enter a description for the subtask and select Create.
On the board
On the board of your team-managed project, next to Group by, select Subtask (project admins only).
Select Create issue (+) to create a subtask under that issue.
View subtasks on the board
Note that only the project admin can access this setting.
Navigate to the board in your team-managed project.
In the Group by dropdown, select Subtasks. The headers for each swimlane will be your regular issues, and the cards underneath each header represent your project's subtasks. You can then move those subtasks between columns like you would any other issue.
When a parent issue is cleared, its subtasks are also cleared, regardless of each subtask’s status. This means that if a subtask belongs to a parent issue that’s been cleared from the board, the subtask won’t be visible.
Was this helpful?