Skip to main content
Skip table of contents

Checklists in Place of Subtasks

A checklist item can be instantly converted to a new work item or a subtask at any time.

A checklist is a simple, but powerful solution to managing the multiple steps involved in completing a Jira work item. Using checklists in lieu of subtasks can help keep your board uncluttered and your Jira instance from becoming bloated.  

Both allow you to…

If you’re not sure you can start with a checklist (the simplest solution) and if needed convert an item to a Jira work item, or convert all incomplete checklist items into subtasks.‍

Here are a few things to consider when deciding whether to use a checklist or subtasks:

  • When you want to keep focus on the entire story CHECKLIST
    Using a checklist keeps everyone who is contributing to the work item on the same page. If you don’t need separate comments or attachments for particular items, then stick with a checklist. This is the most open and transparent way to work.

  • When you want to keep your board clean CHECKLIST
    Subtasks can complicate search and clog up your board. Checklists allow you to define and standardize processes without showing every step to everyone.

  • When you want to estimate and track time on the story CHECKLIST
    If your team uses story points, Jira assumes that the number of story points will be recorded only on the parent issue (typically a Story). If you want to include story points on each subtasks with the total automatically shown on the parent issue, you’ll need to set up automation. In this case, using a single issue with a checklist may be simpler.

  • When you want to repeat the same steps on multiple work items CHECKLIST
    If you’re going to be using the same set of steps on multiple work items, you can easily create a checklist template which can be instantly applied to any work item.

  • When you want to collaborate on the individual step? SUBTASK
    Will multiple team members be collaborating around a single step? Do they need to upload attachments for everyone to view and discuss? Will solutions be proposed and decided upon in the comments section? In this case, you’ll want a subtask to contain all of the needed input.

  • When you want to track time against the individual step? SUBTASK
    If you want to estimate and track time agains each step, use subtasks.

  • When you want step needs to be reviewed and/or approved by someone? SUBTASK
    Since a subtask acts like a regular work tiems going the Jira workflow, it can be reviewed, approved, or sent back to a previous status to be reworked.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.