JIRA - Create a Subtask

Jira - Creating and Using Subtasks

A subtask in Jira is a work item that is part of a larger parent issue. Subtasks are used to break down complex issues (like stories, tasks, or bugs) into smaller, manageable pieces. This allows for better tracking of progress, distribution of work among team members, and more granular estimation.

For example, a ‘Develop new feature’ parent task might have subtasks like ‘Design UI’, ‘Implement backend logic’, ‘Write unit tests’, and ‘Prepare documentation’. Each subtask can be assigned and tracked individually.

Key Characteristics of Subtasks

Consider these points when working with subtasks:

• Parent-Child Relationship: Subtasks are always linked to a parent issue and cannot exist independently.
• Visibility: Subtasks are typically displayed within a dedicated section on the parent issue’s view page.
• Project Context: Subtasks always belong to the same project as their parent issue.
• Independent Fields: While inheriting some context from the parent, subtasks are distinct issues. They can have their own assignee, due date, priority, status (within a workflow), and other field values. The fields available on a subtask are determined by its specific subtask issue type and associated screen configurations.
• No Sub-Subtasks: Standard Jira functionality does not allow subtasks to have their own subtasks (i.e., only one level of subtask hierarchy).
• Workflow Impact: Often, a parent issue cannot be closed or resolved until all its subtasks are completed. This behavior can be enforced by workflow conditions.

Steps to Create a Subtask

Follow these general steps to create a subtask:

1. Open the parent issue to which you want to add a subtask.
2. On the issue view page, look for an option to create a subtask. This is often found under the ‘More’ actions menu (…), as a dedicated ‘Create subtask’ button, or sometimes an inline creation form in the ‘Subtasks’ section of the issue.
3. If you used a menu option, a ‘Create Subtask’ dialog will appear.

The ‘Create Subtask’ dialog will prompt you to enter details for the new subtask. Common fields include:

• Subtask Issue Type: If multiple subtask types are configured (e.g., ‘Technical Task’, ‘Testing Task’), you may need to select one.
• Summary: A concise description of the subtask.
• Assignee: The person responsible for completing the subtask.
• Reporter: Defaults to the current user.
• Other relevant fields like Description, Priority, Due Date, etc., depending on the screen configuration for that subtask type.

After entering the required information, click the ‘Create’ button. The newly created subtask will then appear in the ‘Subtasks’ section of its parent issue. This section typically lists all subtasks, showing their key, summary, assignee, status, and sometimes a progress bar.

Practical Application

Subtasks are highly effective for:

• Breaking Down User Stories: In Agile development, user stories are often broken down into technical subtasks for implementation by different developers or for different parts of the work (e.g., front-end, back-end, testing).
• Detailed Task Management: For any complex task, subtasks provide a way to list out all the individual steps required for completion.
• Tracking Individual Contributions: When multiple people work on one larger issue, subtasks can be assigned to individuals to track their specific responsibilities.
• Creating Checklists: Subtasks can function as a checklist of items that need to be addressed before a parent issue can be considered done.

Proper use of subtasks enhances visibility into the progress of larger work items and helps ensure all aspects of an issue are addressed.