Sub-task issues are useful for splitting up a parent issue into a number of tasks which can be assigned and tracked separately. Splitting issues into smaller tasks often provides a better picture of the progress on the issue, and allows each person involved in resolving the issue to better understand what part of the process they are responsible for. All the sub-tasks related to a parent issue are summarised on the parent issue's main screen (see 'Working with Sub-Tasks' below). Sub-tasks always belong to the same project as their parent issue. Sub-tasks have all the same fields as standard issues, e.g. Summary, Description, Reporter, Assignee, Status. Note that sub-tasks have a different set of issue types from the standard issue types. Sub-tasks cannot have sub-tasks of their own. However, if you need to break up a sub-task into smaller sub-tasks, you could achieve this by first converting the sub-task to a standard issue. You would then be able to create sub-tasks for it. |
Creating a sub-task
To create sub-tasks, you will need to have the 'Create Issue' permission in the parent issue's project. Also note that sub-tasks can only be created if your JIRA administrator has enabled sub-tasks and added the sub-task issue type to the project's issue type scheme.
To create a sub-task:
- Navigate to the issue which you would like to be the parent issue of the sub-task you are about to create.
- From the 'More Actions' drop-down menu, select 'Create Sub-Task'. You will see the 'Create Subtask' screen.
- Fill in the details as needed, and then click the 'Create' button at the bottom of the page.
Tip: You can customise the 'Create Subtask' dialog to show fields you use most often. To do this, at the top right corner of the dialog, click the 'Configure Fields' button, and use the 'All' and 'Custom' links to switch between the default screen and your custom settings. Your changes will be saved for future use.
Note that there is no option to set security on a sub-task, as sub-tasks inherit their parent issue's security levels if any have been set.
What a sub-task looks like
In the following screenshot, the sub-task is DEMO-6 (Enter competition) and its parent issue is DOVE-3 (Win 'homing dove' contest). Both belong to the Demonstration project.
Screenshot: Example sub-task
Working with sub-tasks
If an issue has sub-tasks, then the issue screen will show a list of all the issue's sub-tasks:
Screenshot: An Issue's Sub-Tasks

- Show open sub-tasks only. – The sub-task list has two views: 'All' and 'Open'. The All view lists all sub-tasks, regardless of status, while the Open view only shows sub-tasks that have not been resolved (i.e. do not have a Resolution ). You can switch views by clicking the 'All' and 'Open' links.
- Time-tracking. – The coloured bars show the time-tracking data for the issue and its sub-tasks.
- Reorder sub-tasks. – You can reorder sub-tasks, for example, organise the list in the order of intended execution or priority. Hover your mouse over the sub-task you wish to move, and use the 'up' and 'down' arrows that will appear.
- Perform actions on sub-tasks. – To preform actions on the sub-tasks, e.g. 'Assign Issue', 'Resolve Issue', 'Close Issue', 'Reopen Issue', hover your mouse over the sub-task you wish to action, and click the 'Actions' drop-down menu link that appears.
- Quickly create sub-tasks. – Once an issue has one or more sub-tasks, you can quickly create additional sub-tasks by clicking the '+' icon.
Searching for sub-tasks
When sub-tasks are enabled, two extra entries will appear in the 'Issue Type' drop-down list in the Issue Navigator's search form. These entries are: 'Standard Issue Types' and 'Sub-Task Issue Types'.
- To search standard issues only, click the Standard Issue Types entry.
- To search sub-task issues only, click Sub-Task Issue Types entry.
- To search for one specific type of issue or sub-issue, select just one Issue Type or one Sub-Task Issue Type.
If no entries are selected from the 'Issue Type' drop-down then the search will return all the standard issues and sub-task issues that meet the rest of the search criteria.
Once you have added the 'Sub-Tasks' column to your Issue Navigator, the search results indicate sub-task issues by displaying the parent issue's issue key above the sub-task's summary, as shown below:

Adding the 'Sub-Tasks' column to your Issue Navigator
To add the 'Sub-Tasks' column to your Issue Navigator as shown in the above screenshot, please see Customising your Issue Navigator columns.
Converting a standard issue to a sub-task
- Navigate to the issue which you would like convert to a sub-task.
- From the 'More Actions' drop-down menu, select 'Convert to sub-task'.
- The 'Step 1. Select Parent Issue and Sub-Task Type' screen will be displayed. Type or select the appropriate parent issue type, select the new issue type (i.e. a sub-task issue type) and click the 'Next' button.
- If the issue's current status is not an allowed status for the new issue type, the 'Step 2. Select New Status' screen will be displayed. Select a new status and click the 'Next' button.
- The 'Step 3. Update Fields' screen will be displayed. If the new issue type requires any additional fields, you will be prompted to enter them (otherwise you will see the message 'All fields will be updated automatically'). Click the 'Next' button.
- The 'Step 4. Confirmation' screen will be displayed. If you are satisfied with the new details for the issue, click the 'Finish' button.
- The issue will be displayed. You will see that it is now a sub-task, that is, its parent's issue number is now displayed at the top of the screen (see 'Creating a sub-task' above).
Note that you will not be able to convert an issue to a sub-task if the issue has sub-tasks of its own. You will first need to convert the issue's sub-tasks to standalone issues (see below); you can then convert them to sub-tasks of another issue if you wish. Sub-tasks cannot be moved directly from one issue to another — you will need to convert them to standard issues, then to sub-tasks of their new parent issue.
Converting a sub-task to a standard issue
- Navigate to the sub-task issue which you would like convert to a standard issue.
- Select 'Convert to issue' from the 'More Actions' drop-down menu.
- The 'Step 1. Select Issue Type' screen will be displayed. Select a new issue type (i.e. a standard issue type) and click the 'Next' button.
- If the sub-task's current status is not an allowed status for the new issue type, the 'Step 2. Select New Status' screen will be displayed. Select a new status and click the 'Next' button.
- The 'Step 3. Update Fields' screen will be displayed. If the new issue type requires any additional fields, you will be prompted to enter them (otherwise you will see the message 'All fields will be updated automatically'). Click the 'Next' button.
- The 'Step 4. Confirmation' screen will be displayed. If you are satisfied with the new details for the issue, click the 'Finish' button.
- The issue will be displayed. You will see that it is no longer a sub-task, that is, there is no longer a parent issue number displayed at the top of the screen.







35 Comments
Hide/Show CommentsOct 12, 2010
Yulian Fedulov
Quick question, is there anyway to make one subtask dependent on one another. So one is not able to start one task until another finishes, and also make tasks that are able to be completed at the same time. And also produce a project plan / Gantt chart from that data?
Thank you
Oct 14, 2010
Rosie Jameson [Atlassian Technical Writer]
You may like to take a look at the available plugins: https://plugins.atlassian.com/search/with?q=gantt&product=jira
You may also like to vote for http://jira.atlassian.com/browse/JRA-13362
Dec 09, 2010
Ludwig Magnusson
2 questions:
1 . Is there a way to have a default assigne to a sub-task based on the sub taks type? We often have our tasks split into subtaksk that are almost always "design" and "implementation" and they are always assigned to the same person.
2. Can the sub-task section of the edit task view be shown even if there are no sub-task created for the issue yet?
Dec 09, 2010
Rosie Jameson [Atlassian Technical Writer]
Dec 10, 2010
Ludwig Magnusson
Great!
Thank you very much.
Apr 23, 2011
Jacques Chatenet
Thanks!.
The #2 is very useful for heavy subtask user.
It should be an option that Admin can enable/disable from Config screen.
Dec 28, 2010
Laura Jenkins
Question: As part of the workflow for a issue type, can I have subtasks automatically created for this issue when it transitions into that step? So for exampe, let's say I have the issue type New Client and when it gets to the step Requirements Approved, it would create subtasks where those subtasks relate to subsystems of the product that need to have changes made. Could you please tell me if this could be automated and how? THANKS
Oct 30, 2011
Anonymous
bump
Wondering if this is a planned or current feature (yes have searched the FAQ high and low and couldn't find anything on this).
Jan 16, 2012
Anonymous
This plugin that is maintained by Bob Swift will provide the functionality you're looking for. Sure would be nice if it was part of Jira by default. Maybe one day...
https://plugins.atlassian.com/697735
Jan 19, 2011
Anonymous
Is it possible to have custom fields displayed in the Add Sub-Task form to facilitate rapid entry of subtask including populating my custom field?
Apr 23, 2011
Jacques Chatenet
Seems what you are looking for :
http://confluence.atlassian.com/display/JIRA/Configuring+Sub-tasks#ConfiguringSub-tasks-Choosingwhichfieldstodisplayinthe%27AddSubTask%27form
Choosing which Sub-Task fields to display on the Parent Issue
jira.table.cols.subtasksChoosing which fields to display in the 'Add Sub-Task' form
jira.subtask.quickcreateform.fields(for a list of available fields to include, see Displaying Search Results in XML)Jan 20, 2011
Anonymous
My problem with sub-tasks is that the parent task still has to be tracked separately. For example in a Greenhopper view, the parent task needs to be dragged between swimlanes along with its subtasks. Once a task is broken into subtasks, it's progress should be tracked solely by it's subtasks. Maybe I'm just missing something since I'm still new at this Greenhopper and Jira 4 thing :)
Feb 17, 2011
Anonymous
I would like to have a 'story' be a task and a sub-task. Sometimes a story is part of an epic (e.g. subtask), sometimes it stands-alone (standard). Is this possible?
Mar 16, 2011
Jacques Chatenet
After creating sub-tasks, is there any native feature to ease the management of their relationship with their parents?
Typically, Auto-adjust parent issue on sub-task status
as submitted here http://jira.atlassian.com/browse/JRA-13012
and discussed here : Parent issue state change based on Sub-task progress
http://forums.atlassian.com/thread.jspa?messageID=257242728�
Especially that we dont' find yet a way to filter Issues that have their subtasks started or all closed.
So far, our feature writers have to scan regularly their issues to detect which features can be closed.
(current workaround is to filter all issues and display column subtasks... and scan visually...)
May 04, 2011
Alexander Bondarchuk
Hi! How many levels of subtasks can be created? Thanks.
May 13, 2011
Tobias Janiesch
Hi Alexander, only one level of subtasks can be created. There might be external plugins which could give you that function.
Nov 09, 2011
Anonymous
Hi,
Do you know any of those plugins? We are using Jira heavily and we need desperately several levels of subtasks.
May 13, 2011
Tobias Janiesch
is there a good plugin to have subtasks cross-projects.. so that we can create subtasks in a different project than the parent issue? i only asking for the solution or the plugin, not if it makes sense to have this function.
May 17, 2011
Larina Langdon
agreed, I have an immediate need to add technical tasks to user stories within Jira. What is the plugin that would allow me to create a user-story (sub task) and then would allow me to create tasks or technical tasks under that user story?
Please advise, thanks!
May 18, 2011
Anonymous
We are running JIRA version 4.2.4 with the agile plugin installed and are not seeing the options to create a sub-task. The other agile features are all here, but no sub tasks. Is this a feature that is only available in a later version? Do we need to be on 4.4?
Jul 05, 2011
Anonymous
Is it possible to have a SubTask linked to another project?
Jul 18, 2011
Anonymous
Hi,
Is there a way to bulk change the parent user story of sub tasks?
Thank you,
Chinthaka
Jul 20, 2011
Anonymous
Hi, Is there any way to do a bulk "Convert to Sub-task" operation? We are heavy subtask users and we waste a lot of time adding subtasks to existing tasks manually.
Thank you.
Jul 31, 2011
Anonymous
Hi All, just wondering if there is a way to change sub-tasks from having their own pre-fix which doesnt relate to the parent issue to one that does?
for example if i have an 'issue' called "xyz Company" and it gets prefix C-1 is it possible for all sub-tasks for this Company/'Issue' to have a pre-fix along the lines of;
C-1-a - first sub-task
C-1-b - second sub-task
or
C-1-1 - first sub-task
C-1-2 - second sub-task
Oct 20, 2011
Anonymous
I was going to submit this as a suggestion but saw it here.
It is very frustrating when doing a bulk search on issues but not having sub-tasks appear immediately under their related issue.
Aug 11, 2011
Anonymous
emphtedHi,
I'm also interested to know if a task of project x can be made a subtask of project y.
Aug 17, 2011
Anonymous
One good idea is to not allow parent tasks to be closed unless all subtasks are completed. Another nice option would be to allow a setting to automatically mark the parent as complete if all the subtasks are complete.
Aug 23, 2011
Anonymous
Hey y'all,
I'd like to assign my co-worker to a sub-task. However, the only dropdown options I get are "Automatic" & JIRA Admin (that's me). I wonder how I can make her the Assignee?
Thanks a lot!
Cheers
Aug 23, 2011
Anonymous
Solved it myself. Thans anyway!
Sep 21, 2011
Anonymous
Hi all,
I was wondering how can I make a subtask inherit all or some of the pre-defined values from it's parent (story in my case). For example, if i create a sub-task, i would like to already have the components and the versions inherited from it's parent. Is that possible? In Greenhopper, when adding a sub-task all these fields are inherited but not when you use "Create Issue" screen. I have another problem with Greenhopper and I can't use that screen either.
Thanks!
Sep 29, 2011
Anonymous
When I size an issue, and later make that issue a sub-task, I lose the sizing information and it is marked 'N/A' on the Planning Board. The sizes don't roll up into the parent story or epic, either. Is there a way to do that?
Thanks.
Oct 05, 2011
Anonymous
Hi!
Is there a way to customize it the time tracking on the task/sub task relation. For example, the default, after we enter a new sub task and that has an estimate of 2h, then 2h are added to the original estimate of the parent main task. Is there a way to change that so that the estimated time on the sub task does not add to the main task? We want to keep our main task with a defined original estimate, but be able to add sub tasks with its own estimates, but without raising the original estimate for the main task/story.
Oct 28, 2011
Anonymous
Hi,
I'd like to have the process steps (such as Write Cunit test, iImplement, integrate to trunc) included when creating storys Is there a way to do this? One way would be to automatically create sub-tasks for each of those process steps but can not see that this is possible. Any ideas?
Thanks.
Dec 26, 2011
Anonymous
Hi,
I'd like to convert a "task" (which was already closed) to a "sub-task".
I could not convert it as "convert to sub-task" option is not available under "more actions" menu for closed tasks.
I then re-opened the task and tried again, but result was the same.
I would be very pleased if you could inform me whether this is possible.
Regards,
Eregun Seray
Jan 30, 2012
shlomi asaf
Hi
I don't have any subtask option in my menu. How come? Can anybody help?
Add Comment