Creating a subtask in Jira takes three steps: open the parent issue, click Create Subtask, and fill in the summary and assignee

A subtask in Jira is a smaller piece of work that belongs to a larger issue. If you have a task called "Build login page," you might create subtasks for "Design form fields," "Write validation code," and "Test on mobile." Subtasks help break work into pieces that one person can finish, and they roll up into the parent issue's progress.

You create a subtask from inside the parent issue itself — not from the board or the issue list. Once you create it, the subtask appears as a linked item on the parent issue, and you can assign it to a team member, set a due date, and track it separately.

Key Takeaways

  • Subtasks are created from inside the parent issue by clicking the Create Subtask button, not from the board view.
  • You must fill in at least the Summary field; other fields like Assignee and Due Date are optional but recommended.
  • Subtasks inherit the project and issue type settings from the parent, so you cannot change the project after creation.
  • Deleting a subtask does not affect the parent issue, but deleting the parent issue deletes all its subtasks.

Open the parent issue and locate the Create Subtask button

Start by navigating to the issue that will be the parent. Click on it to open the full issue view — not the card on the board, but the detailed page where you see the description, comments, and linked items.

Look for the Create Subtask button. In most Jira layouts, it appears in the Actions menu at the top right of the issue, or as a standalone button near the issue details. If you do not see it immediately, click the three-dot menu (⋯) or the Actions dropdown to find it. Some Jira instances place it in the issue's toolbar; others put it in a sidebar. The exact location depends on your Jira version and your team's configuration.

Fill in the subtask details

When you click Create Subtask, a form appears. The Summary field is required — this is the title of your subtask, like "Write database schema" or "Update documentation." Keep it short and specific so your team knows exactly what needs to be done.

The Assignee field is optional but important. Click the field and type or search for the team member who will do this work. If you leave it blank, the subtask stays unassigned until someone claims it. The Due Date field lets you set when the subtask should be finished; this is also optional but helps with planning.

Other fields like Priority, Description, or Labels may appear depending on your Jira setup. Fill in what your team needs. If a field is required (marked with a red asterisk), you cannot create the subtask without it.

Submit the subtask and verify it appears on the parent

Click the Create button at the bottom of the form. Jira saves the subtask and returns you to the parent issue. Scroll down to the Subtasks section — you should see your new subtask listed there with its summary, assignee, and status.

The subtask now appears as a separate item in Jira. It has its own issue key (like PROJ-123.1) and shows up in searches, reports, and on the board if your board is configured to display subtasks. The parent issue's progress bar updates to reflect the subtask's status as it moves through your workflow.

What happens if you cannot see the Create Subtask button

If the Create Subtask button is missing, your Jira administrator may have disabled subtasks for your project or issue type. Check with your team lead or administrator to confirm subtasks are turned on.

Another reason the button might not appear is permissions. Your Jira account may not have permission to create subtasks in this project. Ask your administrator to check your role and grant the Create Issue permission if needed.

If subtasks are enabled and you have permission, try refreshing the page or logging out and back in. Sometimes the interface does not load completely on the first try.

Editing and deleting subtasks

Once a subtask exists, you can edit it by clicking on it to open its own issue page, then clicking Edit. You can change the summary, assignee, due date, and other fields the same way you would edit a regular issue.

To delete a subtask, open it and look for the Delete option in the Actions menu. Deleting a subtask removes it from the parent issue but does not affect the parent itself. However, deleting the parent issue deletes all its subtasks automatically, so be careful when removing a parent.

Common mistakes when creating subtasks

The most common mistake is creating too many subtasks or subtasks that are too small. If every subtask takes less than an hour, you are probably breaking the work down too far. Subtasks should represent a meaningful piece of work that one person can own and finish in a day or two.

Another mistake is leaving subtasks unassigned. An unassigned subtask often gets overlooked because no one knows it is their responsibility. Always assign a subtask to someone, even if you have to reassign it later.

Do not create a subtask and then forget about it. Once you create a subtask, it becomes part of your team's workload. Check in on subtask progress during standups or reviews so they do not slip through the cracks.

Frequently Asked Questions

Can I create a subtask of a subtask?

No. Jira only allows one level of subtasks. A subtask cannot have its own subtasks. If you need more layers of breakdown, consider using linked issues instead, which let you connect issues in a parent-child relationship without the subtask limitation.

What happens to subtasks when I move the parent issue to a different project?

Subtasks stay in the original project and remain linked to the parent issue. The parent issue itself moves, but the subtasks do not follow. This can cause confusion, so avoid moving issues with subtasks unless you are certain your team understands the setup.

Can I change the issue type of a subtask after I create it?

No. The subtask issue type is set when you create it and cannot be changed afterward. If you need a different issue type, delete the subtask and create a new one with the correct type.

Do subtasks count toward my team's velocity or sprint capacity?

That depends on your team's Jira configuration. Some teams count subtask story points toward velocity; others count only the parent issue. Ask your Scrum Master or team lead how your instance is set up.

What if I need to assign a subtask to multiple people?

Jira subtasks have a single Assignee field, so you cannot assign one subtask to two people directly. If the work truly needs two people, either split it into two separate subtasks or use the Description or Comments to note who else is involved.