Jira Issues Explained: Types, Fields, and Examples for Agile Teams
What is a Jira issue, and how can it help your team? Explore issue types, fields, and examples to make Agile work clearer. Read now.
A Jira issue is a trackable work item that represents something a team needs to complete, investigate, or resolve. It might be a user story, task, bug, or larger initiative.
If your team creates issues without clear types or useful details, work can become hard to prioritize and easy to misunderstand. A bug might lack steps to reproduce it, or a task might have no clear owner. Those gaps create extra questions during planning and delivery.
But here's the truth: Jira issues are more than cards on a board. They connect work to owners, status, priorities, and team plans. Once you understand their types and fields, you can create issues that give everyone a clearer next step.
What Is a Jira Issue?
A Jira issue is an individual work item that a team tracks through a workflow. It has an issue type, a unique identifier, and fields that describe its purpose, owner, priority, and current status.
For example, a team might create a bug called “Checkout button does not respond on mobile.” The issue can capture how to reproduce the problem, who will investigate it, and whether it is still open or ready for review.

What a Jira issue contains
- Issue type: Identifies the kind of work, such as a story, task, or bug.
- Summary: Gives the issue a short, scannable title.
- Description: Explains the need, problem, or expected result.
- Status: Shows where the work sits in the team’s workflow.
- Assignee: Names the person responsible for progressing it.
- Priority: Signals how urgently the team should address it.
Jira assigns each issue a unique key, such as SHOP-42. That key helps teammates find and discuss the same item across boards, project views, and conversations.
Common Jira Issue Types and When to Use Them
Issue types give your team a shared way to classify work. The available types can vary by project configuration, so check which options your Jira project provides.
Here's why: choosing a type affects how people interpret an issue and how the team organizes it. A bug usually needs a clear account of unexpected behavior, while a story describes a user need.
- Epic: A larger goal that can group related work. For example, “Launch customer loyalty” might contain several stories and tasks.
- Story: A piece of functionality described from a user’s perspective. For example, “As a shopper, I want to save my address for checkout.”
- Task: A defined piece of work that may not describe a user-facing feature, such as reviewing a deployment process.
- Bug: An issue that records behavior that does not work as expected, such as a checkout button failing on a phone.
- Sub-task: A smaller piece of work attached to a parent issue, such as writing test cases for a story.
Let me explain: an epic is usually a larger container, while stories, tasks, and bugs describe work that can move through a team’s workflow. Sub-tasks help divide a parent issue when one person or one step cannot cover the work cleanly.
For example, a team improving account security could create an epic, then add stories for two-factor sign-in and recovery options. A bug discovered during testing could remain its own issue and link to the related story.
Jira Fields That Make Issues Useful
Fields add context that helps a teammate understand what needs attention. Some fields appear by default, while others may be customized for a project or workflow.
The best part? A concise issue can still be complete. A clear summary, a useful description, and a named owner often prevent more confusion than a long list of empty fields.
- Summary: Use a specific title, such as “Show an error when a payment card is declined.” Avoid vague titles like “Payment problem.”
- Description: Explain the goal, the current behavior, or the steps needed to investigate.
- Status: Reflect the work’s current stage, such as To Do, In Progress, or Done.
- Assignee: Identify who is responsible for moving the issue forward.
- Reporter: Identify who raised the issue or request.
- Priority: Show the issue’s urgency relative to other work.
- Labels: Add searchable categories, such as “mobile” or “checkout.”
- Sprint: Connect planned work to a sprint when the team uses sprint planning.
- Due date: Record a target date when timing matters.
- Issue links: Show relationships, such as work that blocks or depends on another issue.
For a bug, a strong description might include the device, the action that triggers the problem, and the result you expected. For a story, explain who needs the feature and what outcome would make it useful.
How Jira Issues Move Through Agile Work
An issue typically moves through a workflow as a team plans, performs, and reviews the work. The exact status names depend on the project, but the process often starts with an issue awaiting attention and ends when the team considers it complete.
You might be wondering: does every issue belong in a sprint? No. Teams can keep future work in a backlog and select suitable issues during planning. A sprint field becomes useful when the team commits work to a particular sprint.
- Create or capture the work: Write a summary and enough description for a teammate to understand the request.
- Classify and prioritize: Choose an issue type and decide how it compares with other work.
- Plan ownership: Assign the issue or leave it for the team to pick up during planning.
- Update progress: Move it through the workflow as work advances.
- Review and complete: Confirm the expected result, then move the issue to the appropriate final status.
For example, a team may create a story in its backlog, discuss it during planning, assign it to a sprint, and move it through development and review. A related bug could be prioritized separately if it needs urgent attention.
A Jira Issue Example for an Agile Team
Imagine that shoppers report trouble applying discount codes on mobile. A vague issue titled “Discounts broken” leaves the team guessing. A useful bug gives them a concrete problem to investigate.
Example bug issue
- Type: Bug
- Summary: Discount code is rejected on mobile checkout
- Description: On a mobile device, enter a valid discount code at checkout. The page displays an “invalid code” message, although the same code works on desktop.
- Priority: High, if the issue affects a large number of shoppers or blocks purchases.
- Assignee: The teammate responsible for investigating checkout behavior.
- Labels: mobile, checkout, promotions
- Related work: Link the issue to a checkout improvement story if one exists.
This example gives the team a reproducible symptom and a starting point for investigation. It avoids guessing at the fix before someone has confirmed the cause.
For a feature request, the team could create a story such as “As a shopper, I want to see when a discount code expires.” The description could explain the expected message, while acceptance criteria clarify what the team will test.
Jira Issue Management with ONES.com
ONES.com brings project management and knowledge management together in one platform, powered by ONES Assistant. ONES Project is the project management product and Jira alternative; ONES Wiki is a separate knowledge management product and Confluence alternative. They are sold separately.

Value proposition
Teams can manage issues with configurable workflows, fields, sprint planning, automation, and reporting. Cloud and self-hosted deployments have feature parity, giving teams deployment choices without changing the available feature set.
Core capabilities
- Issue organization: When work is scattered across disconnected processes, ONES Project brings project work into a shared project management environment, helping teammates see progress in context.
- Jira-compatible workflows: When teams need familiar issue flows, Jira-compatible workflows help them adapt processes and maintain continuity.
- Custom workflows and fields: When a generic issue form misses important context, teams can configure workflows and fields to match their process.
- Sprint management: When a team plans work in iterations, sprint management supports planning and tracking those commitments.
- Built-in reporting: When progress is difficult to assess, built-in reporting helps teams review project status without relying on a stack of add-ons.
- Automation: When routine updates take time, automation can handle configured workflow actions and reduce manual follow-up.
- Deployment options: When hosting requirements differ, teams can choose Cloud, On-Premise, Private Cloud, or Air-gapped deployment.
- Knowledge management: When project decisions need a separate knowledge base, teams can use ONES Wiki as a separately sold product alongside ONES Project.
Application scenarios
A software team moving from Jira can assess ONES Project’s compatible workflows, custom fields, sprint management, and reporting against its existing processes. Its free plan supports up to 30 seats, which can help a small team evaluate the product before deciding how to proceed.
A team with restricted hosting requirements can consider On-Premise, Private Cloud, or Air-gapped deployment. Teams that prefer hosted service can choose Cloud. This range can matter when project work must stay within a specific operating environment.
For teams that use Jira today, the practical question is whether ONES Project can support the workflow they need with fewer plugins and the deployment arrangement they require. ONES.com also offers full feature parity between its cloud and self-hosted versions.
Common Challenges When Working with Jira Issues
Even a well-known issue tracker can become confusing when teams create inconsistent records or leave work without a clear owner. These fixes can make everyday issue handling more reliable.
- Problem: Issues have vague summaries. A title like “Fix page” gives little direction. Solution: State the affected area and the observed problem, such as “Search results disappear after changing filters.”
- Problem: Descriptions omit useful context. Teammates have to ask the same follow-up questions. Solution: Add relevant steps, expected behavior, and actual behavior, especially for bugs.
- Problem: Work has no clear owner. An issue can remain untouched when everyone assumes someone else will handle it. Solution: Assign responsibility during planning or agree how the team will select unassigned work.
- Problem: Teams use issue types inconsistently. Similar work gets classified in different ways, making planning harder. Solution: Agree on simple examples of when to use stories, tasks, bugs, and sub-tasks.
- Problem: Status no longer reflects progress. Teammates cannot tell whether an issue is active or waiting. Solution: Update status when work changes stage and clarify what each status means to the team.
Frequently Asked Questions About Jira Issues
Is a Jira issue the same as a task?
No. “Jira issue” is a broad term for a trackable work item. A task is one possible issue type, alongside stories, bugs, epics, and sub-tasks. The types available to you depend on your project’s setup. For instance, a team might track a software defect as a bug and a routine maintenance activity as a task.
What is the difference between a Jira issue and an epic?
An epic is a type of Jira issue that usually represents a larger goal or body of work. Teams can associate related stories, tasks, or bugs with it, depending on their project configuration. For example, “Improve account security” could be an epic with separate issues for sign-in verification and account recovery.
Can I change a Jira issue’s type?
In many Jira projects, an issue type can be changed, but available actions depend on permissions and project configuration. Before changing it, consider whether the new type fits the work and whether the change affects fields or workflow steps. If the option is unavailable, ask a Jira administrator or project lead about the project’s rules.
What should I include in a Jira bug issue?
Give the bug a specific summary, then describe what happened and what you expected instead. Add steps to reproduce the behavior, along with relevant context such as device or browser when it matters. A useful example is “On mobile Safari, submitting a valid discount code shows an error.” This gives the team a clear place to begin.
Conclusion
Jira issues help agile teams describe, assign, prioritize, and track work. Understanding the difference between issue types and completing the right fields makes planning clearer and reduces avoidable follow-up questions.
If vague titles, missing context, or unclear ownership are slowing your team down, agree on a few simple issue-writing habits. Start with a specific summary, choose the right type, and explain enough for the next teammate to act. You can also evaluate ONES Project if you need a Jira alternative with configurable workflows and multiple deployment options.