JIRA Sub-Task with Example (JIRA Create Sub-task)

Handling Sub-tasks and Combining Tasks in JIRA:

In our last tutorial, we explored the JIRA Bug Tracking Instrument.

Even though JIRA issues are usually individual tasks, it is feasible to fragment them into tinier sub-tasks.

There are numerous methods to accomplish this. One alternative is copying issues, meaning users don’t need to input all the fields again to create a similar issue. The JIRA Instruction Series offers comprehensive details on this concept.

=> Access Here For Comprehensive JIRA Tutorials Series

This guide elaborates on JIRA Sub-tasks, how to create a JIRA sub-task, converting an issue into a sub-task, reproducing an issue, and shifting an issue.

A sub-task is a fractional division of a main issue (task) into smaller work segments that can be allotted and monitored individually.

Sub-Tasks In JIRA

In JIRA, a task/issue symbolizes a specific narrative or requirement to be processed.

For larger and more complex issues, JIRA permits their division into logical sub-issues which are known as ‘Sub-tasks’. These minor issues can be managed more effectively.

Each sub-task can be allocated to a different individual, facilitating better progress tracking of the main issue. Furthermore, working on a sub-task offers a more precise understanding of the specific area being tackled.

Once the sub-tasks are generated, the main issue is regarded as the parent issue. All sub-issues of the central issue are presented as a summary on the same page/screen within the ‘Sub-Tasks’ section.

=> It is critical to bear in mind that a sub-task holds all the identical fields as a standard issue, however, sub-tasks possess different issue types.

Varieties Of Sub-Tasks

(This list can differ from one organization to the next)

• Sub-task
• Merge-To_Branch Sub-task
• RCA

Procedure To Construct A Sub-Task

#1) Launch the issue for which the sub-task(s) need to be generated

#2) Click the ‘…’ (ellipsis) button in the upper-right corner to widen the drop-down menu.

#3) Select the ‘Create Sub-task’ option (refer to the image below for the ‘ellipsis’ button and menu item).

This will open the ‘Create Subtask’ pop-up page.

Note: The ‘Create Sub-task’ submenu should be activated by a JIRA administrator. Additionally, the sub-task issue type needs to be incorporated into the issue type scheme of the project.

Note: In earlier versions of JIRA, the ‘…’ button was labeled as ‘More’ and positioned alongside buttons like ‘Edit’ on the toolbar.

In the ‘Create Subtask’ pop-up page, choose ‘Sub-task’ in the issue type drop-down, fill in the obligatory fields, offer input for any extra fields, and click the ‘Create’ button at the bottom of the page.

The freshly created sub-task will be shown in the ‘Sub-tasks’ section of the parent issue.

Note: The fields on the ‘Create Subtask’ pop-up page can be modified to exhibit widely utilized fields. This can be done by clicking the ‘Configure Fields’ option (illustrated by a wheel icon) in the top-right corner of the page.

Another sub-issue type is the ‘MergeToBranch-Subtask’, used particularly when shifting/merging code from one project/product branch to another. For instance, when moving from a development branch to a branch already in production, this sub-task type is widely employed.

The process for creating a merge-type sub-task is the same as for an ordinary sub-task, except that the ‘MergeToBranch-Subtask’ option should be chosen in the issue type drop-down. Once the merge-to-branch issue is generated, the code move should ideally be endorsed by the product owner.

Note: Sub-tasks cannot be further fragmented into additional sub-tasks. If further disintegration is needed, the sub-task should be transformed into a standard issue, which can then have its sub-tasks.

In summary, an issue can be transformed from a standard (standalone) issue into a sub-task and vice versa. However, if an issue already carries sub-tasks