#1 India's Top IT Training Institute
×

About Uncodemy

Know more about who we are and what we stand for.

About Us

About Us

Discover our mission to equip individuals with essential IT skills and industry expertise.

Read More →
UnCodeMy Gallery

UnCodeMy Gallery

Explore highlights from our IT training sessions and success stories.

Read More →
Mentors

Mentors

Meet the industry experts who train and guide you through your course.

Read More →
Free Resources

Free Resources

Free tutorials, interview questions, tools and calculators to help you learn.

Explore →
×

Free Resources

Learn, practice and plan your career — bilkul free.

Tutorials

Tutorials

Step-by-step written tutorials to learn any technology at your own pace.

Read More →
Free Counselling

Free Counselling

Book a free video counselling session and pick the right course for you.

Read More →
Online Compiler

Online Compiler

Write, run and test your code online — no setup required.

Read More →
Issue Management

Issue Types - Epic, Story, Task, Bug

Every piece of work in Jira is represented as an issue, and Jira offers several issue types to represent different levels and kinds of work. Understanding these types helps your team structure projects clearly and report on progress accurately.

The Issue Hierarchy

An Epic represents a large body of work, such as a new product feature, that is broken down into smaller Stories. A Story describes a piece of functionality from the user's perspective, while a Task represents a general piece of work that doesn't need to be framed as a user story.

Where Bugs Fit In

A Bug is an issue type reserved for defects — something in the product that isn't working as intended. Keeping bugs separate from stories and tasks makes it easier for teams to track quality issues and prioritize fixes alongside new feature work.

Common Jira Issue Types

  • Epic — a large initiative broken into smaller stories
  • Story — a feature described from the user's point of view
  • Task — a general unit of work for the team
  • Bug — a defect that needs to be fixed
  • Sub-task — smaller work items nested under a parent issue

Worked Example: Breaking Down an Online Payments Feature

Imagine a shopping team planning card and UPI payments. The work could be structured like this:

Issue typeExample summaryWho it serves
EpicSHOP-12 Online payments at checkoutThe business goal
StoryAs a shopper, I want to pay by UPI so that I can check out without a cardThe end user
StoryAs a shopper, I want to save my card so that repeat purchases are fasterThe end user
TaskSet up sandbox account with the payment gatewayThe team
Sub-taskWrite API tests for the payment callbackPart of a story
BugOrder total shows wrong amount after applying a coupon with UPIQuality

The epic closes only when its stories are done, which gives managers a simple way to see progress on the bigger goal.

Writing Each Type Well

Stories

Use the format "As a [user], I want [action] so that [benefit]", then add acceptance criteria that testers can check. For the UPI story: payment succeeds with a valid UPI ID, an invalid ID shows a clear error, and a timeout leaves the order unpaid rather than duplicated.

Tasks

Tasks describe technical or operational work with no direct user-facing behaviour, such as upgrading a library or configuring a server. Keep the summary action-oriented: "Configure", "Migrate", "Document".

Bugs

A useful bug includes environment, build or version, steps to reproduce, expected result, actual result and evidence such as screenshots or logs. Link it to the story it affects so the relationship shows up on both issues.

Sub-tasks

Sub-tasks split one story or task among people or skills, for example frontend, backend and testing. They cannot exist without a parent and normally share its sprint.

Finding Work With JQL

Jira Query Language lets you filter issues by type. A few practical queries:

project = SHOP AND issuetype = Bug AND status != Done ORDER BY priority DESC
parent = SHOP-12
project = SHOP AND issuetype in (Story, Task) AND sprint in openSprints()
project = SHOP AND issuetype = Bug AND created >= -7d

The second query lists everything under the payments epic. Saving such queries as filters lets you place them on dashboards.

Choosing the Right Type and Avoiding Misuse

  • If the item changes what a user can do, it is usually a story.
  • If it is needed work with no visible user change, it is a task.
  • If something that should already work does not, it is a bug; a new wish is not a bug.
  • If it spans several sprints and many stories, make it an epic.

Common misuse includes epics that stay open forever because no one defined when they are finished, stories so large they never fit a sprint, and sub-tasks used as a to-do list for unrelated work. Administrators can also create custom issue types, but adding too many confuses reports, so extend the defaults only when a clear need exists.

Master Jira with Expert-Led Training

Hands-on classes, mentor support, and placement assistance — all in one course.

Explore Jira Course