JIRA Subtasks and Links
Big pieces of work rarely stand alone. A login page needs design, coding, and testing. Two bug reports may describe the same crash. Subtasks and issue links let JIRA capture these relationships without clutter.
Subtasks: Breaking One Issue into Small Steps
A subtask is a child issue that lives under one parent issue. It cannot exist alone. The parent can be a story, a task, or a bug. Each subtask carries its own assignee, status, and due date.
Think of a recipe. The dish is the parent, and each cooking step is a subtask. Different helpers handle different steps at the same time.
STORY-10: Build Login Page | +-- Subtask: Design the screen (Asha) Done | +-- Subtask: Write the login code (Ravi) In Progress | +-- Subtask: Test on mobile phones (Meena) To Do
Steps to Create a Subtask
- Open the parent issue.
- Click the option to add a subtask or child issue.
- Type a short summary that names the step.
- Choose an assignee and a due date.
- Save the subtask.
Subtasks and the Parent Status
A parent shows how many subtasks stay open. Many teams add a workflow rule that blocks the parent from closing while any subtask remains open. That rule prevents half-finished work from slipping into Done.
Issue Links: Connecting Separate Issues
A link joins two independent issues and describes how they relate. Both issues keep their own status and owner. The link only records the relationship.
Common Issue Link Types
| Link Type | Meaning | Example |
|---|---|---|
| Blocks / Is Blocked By | One issue stops another from moving forward | A server bug blocks the checkout launch |
| Relates To | Two issues share a topic, with no strict order | Two stories touch the same screen |
| Duplicates / Is Duplicated By | Two issues report the same problem | Two customers report the same crash |
| Clones / Is Cloned By | One issue starts as a copy of another | A fix repeats on a second product |
Link Map Example
BUG-12 "Payment fails" | |-- blocks -------------> STORY-40 "Launch checkout" | +-- is duplicated by ---> BUG-15 "Payment page crashes"
Anyone who opens STORY-40 sees the blocker straight away. The team fixes BUG-12 and closes BUG-15 as a duplicate.
Subtasks vs Links
Subtask and Link Comparison
| Point | Subtask | Issue Link |
|---|---|---|
| Relationship | Parent and child | Peer to peer |
| Can exist alone | No | Yes |
| Projects involved | Same project as the parent | Same or different projects |
| Typical use | Split one item into steps | Show dependencies and duplicates |
| Board display | Appears under the parent card | Appears in the issue detail view |
Choosing the Right Tool
- Pick a subtask when one person or one team finishes all the pieces together.
- Pick a link when work crosses teams or projects.
- Pick a separate story when a piece can ship alone and delivers value by itself.
Best Practices
- Keep each subtask small enough to finish within one working day.
- Limit a parent to roughly three to seven subtasks. Longer lists suggest the parent should split into stories.
- Write summaries that start with a verb, such as "Test payment flow".
- Link blockers early so planning meetings reveal risks sooner.
- Close duplicates with a link and a short comment that points to the original.
Real-World Example: Release Blocker
A team plans a release with five stories. Story four depends on a database upgrade that lives in an infrastructure project. The product owner links the upgrade task to the story with "is blocked by". The release manager filters the board for blocked issues every morning and spots the delay on day one instead of day ten.
Summary
Subtasks break one issue into smaller steps owned by different people. Links connect separate issues that depend on, repeat, or relate to each other. Subtasks stay inside one project, and links cross project borders. A mix of both keeps plans clear and surfaces risks early.