Jira Tickets Explained: Types, Fields, and Real Examples
What is a ticket in Jira? Explore ticket types, key fields, and real examples to clarify work and ownership. Click to learn more.
A Jira board can look simple until a ticket lands in your queue with an unclear title, missing details, and no obvious owner. You may know the team needs to fix something, yet still wonder what the ticket means or what to do next.
That confusion can lead to duplicate work, delayed fixes, and status updates that leave everyone guessing. A ticket is only useful when people can understand the work, see its progress, and know who is responsible.
But here's the truth: Jira tickets follow a practical structure. Once you understand their types, fields, and workflow, you can create clearer work items and move tasks forward with confidence. Here's how to read one, with examples you can adapt.
What Is a Ticket in Jira?
A Jira ticket is a trackable work item in Jira that describes a task, bug, feature, or other piece of work. It has a unique key, details about the work, and a status that shows its progress.
Jira’s interface and teams often call these items “issues.” In everyday conversation, people commonly say “ticket.” For example, WEB-142 might identify a ticket to fix a checkout error.
Each ticket gives a team a shared place to describe work, assign responsibility, discuss changes, and track progress. Its fields and available ticket types can vary by project and workflow.

What a Jira Ticket Contains
A ticket has a summary that names the work and usually a description that explains it. Other fields can show its type, priority, assignee, status, and related work.
Comments keep discussion close to the task. A ticket’s history can also show status changes and updates, helping teammates understand what happened without chasing a separate conversation.
Ticket, Issue, and Work Item
In Jira, “issue” is the familiar term for an individual item of work. “Ticket” is a common informal name, while “work item” is another general term you may see across project management tools.
For example, a team may create a bug issue, call it a bug ticket in chat, and group it under a broader feature. The labels differ, while the purpose remains clear: track a piece of work through its lifecycle.
Common Jira Ticket Types
Ticket types help you describe the kind of work a team needs to complete. A software team might use stories, tasks, bugs, and epics, while a service team may configure requests or incidents.
Here's why: choosing a suitable type gives teammates useful context before they open the details. A reported error needs investigation; a feature story describes a user need. Their work may follow different steps.
Story
A story describes a feature or user need, often from the perspective of the person who benefits. For example: “As a shopper, I want to save a delivery address so I can check out faster.”
Teams often add acceptance criteria to explain what a successful result looks like. A story may be divided into smaller tasks when several people need to contribute.
Task
A task represents a defined piece of work that does not fit a more specific type. “Update the onboarding guide” or “Review the payment provider settings” could be tasks.
Keep the summary action-oriented. A teammate should be able to tell what needs doing without opening a long discussion.

Bug
A bug reports behavior that is broken, incorrect, or different from what the team expects. Useful details include steps to reproduce the problem, the expected result, and what happened instead.
For example, “Discount code disappears after returning to checkout” is more actionable than “Checkout problem.” Add the browser or device when it helps someone reproduce the issue.
Epic and Sub-task
An epic groups a larger body of related work, such as launching a new billing experience. Stories and tasks can sit under it, making progress easier to review at a broader level.
A sub-task breaks one ticket into a smaller piece with its own owner or status. For example, a “Create account settings page” story might have sub-tasks for design, implementation, and testing.
Other Types
Teams can configure additional types, such as incidents, service requests, or changes. The names and behavior depend on the Jira project’s setup.
If a ticket type is unclear, check the project’s guidance or ask the person who manages its workflow. A consistent type helps reports and queues stay useful.
Important Fields in a Jira Ticket
Fields capture the information a team needs to plan, prioritize, and complete work. Some fields appear on nearly every ticket; others show up only for a particular project or ticket type.
The best part? You don’t need to fill every available field with extra detail. Start with what a teammate needs to understand the work and take the next step.
| Field | What it tells you | Example |
| Summary | A short description of the work | “Fix password reset link” |
| Description | Context, steps, requirements, or acceptance criteria | “Link expires before the email arrives” |
| Issue type | The category of work | Bug, story, task, or epic |
| Status | Where the ticket is in its workflow | To Do, In Progress, or Done |
| Assignee | The person currently responsible for the ticket | A developer or support agent |
| Reporter | The person who created or reported the ticket | A customer support teammate |
| Priority | How urgently the team should handle it | High or Medium |
| Labels | Flexible tags for organizing related work | “mobile” or “checkout” |
| Due date | A target date for completing the work | June 18 |
| Sprint | The planned development cycle, when used | “Sprint 24” |
How to Write a Helpful Summary and Description
Use a summary that names the problem or action. “Fix broken reset link on mobile” gives more direction than “Password issue.”
In the description, add the background and details needed to act. A bug report might include reproduction steps, expected behavior, actual behavior, and relevant device information.
For a feature, describe the intended outcome and acceptance criteria. For example, “A signed-in shopper can save up to three delivery addresses” gives the team something concrete to verify.
Priority, Status, and Assignee Are Different
Priority signals urgency; status describes progress; assignee identifies responsibility. These fields answer separate questions, even when people update them together.
A high-priority ticket can still be in To Do, and an In Progress ticket may have a different assignee tomorrow. Keeping each field accurate gives the team a clearer view of its work.
How Jira Tickets Move Through a Workflow
A workflow is the sequence of statuses a ticket can pass through. A simple team might use To Do, In Progress, and Done. Another team may add Review, Testing, or Waiting for Approval.
Let me explain: a status shows the ticket’s current stage, while a transition moves it to another stage. A developer might move a bug from In Progress to Review when the fix is ready.
A Simple Ticket Lifecycle
- Create: Add a clear summary, select a suitable type, and describe the work.
- Plan: Set priority, choose an assignee, and add the ticket to a sprint or queue when appropriate.
- Work: Update the status as progress changes and add relevant comments.
- Review: Check the work against requirements or acceptance criteria.
- Complete: Move the ticket to Done when the team’s completion conditions are met.
Consider a bug where a reset link expires too soon. The reporter adds reproduction steps, a developer investigates it, and the ticket moves through review before closure.
A ticket’s path can differ by team. If a ticket is blocked by a decision or another task, a comment and a clear status update can explain why it has stopped moving.
How Tickets Connect to Each Other
Jira can link tickets to show relationships, such as one task blocking another or two tickets describing related work. An epic can also group several smaller tickets under a broader goal.
For example, a “Launch saved addresses” epic might include a user story, a design task, and a bug found during testing. These connections make dependencies and progress easier to follow.
Real Examples of Jira Tickets
Examples make ticket fields easier to understand. The details below show how a small amount of specific context can turn a vague request into work someone can pick up.
You might be wondering: how much detail is enough? Include enough for a teammate to understand the goal, reproduce a problem, or check the finished result.
| Type | Summary | Useful details |
| Bug | Reset link expires before email arrives | Steps to reproduce, expected and actual behavior, browser, priority |
| Story | Save a delivery address at checkout | User need, acceptance criteria, related design task |
| Task | Review payment provider settings | Scope of review, owner, target date |
| Sub-task | Add address validation message | Parent story, validation rule, completion condition |
Example: A Bug Report
Summary: Reset link expires before the email arrives.
Description: A customer requests a password reset, then opens the email two minutes later. The link has expired, even though the page says it remains valid for ten minutes.
Expected result: The link works for ten minutes. Actual result: It shows an expired-link message after two minutes. These details help a teammate investigate without first asking what went wrong.
Example: A Feature Story
Summary: Save a delivery address at checkout.
Description: A signed-in shopper can save an address and select it on a later order.
Acceptance criteria: The shopper can save an address, edit it, and choose it at checkout. The team can split this story into design, development, and testing tasks if separate owners are involved.
Jira Ticket Practices That Keep Work Clear
Good ticket habits reduce clarification loops and make handoffs smoother. They also help a team scan a queue and see which work needs attention.
For instance, a concise bug report with reproduction steps can save a developer from repeatedly asking the reporter to recreate the issue. A clear owner makes the next action easier to identify.
Write for the Person Picking Up the Work
- Use a summary that names one task or problem.
- Include context that explains why the work matters.
- Add steps to reproduce a bug when possible.
- State how the team can tell a feature is complete.
- Link related tickets when they affect each other.
Keep the description focused on the work. If a ticket combines unrelated requests, split it so each item can have an owner, status, and completion point.
Keep Ticket Details Current
Update status when the work changes stage, and revise the assignee when responsibility moves. Add a comment when a dependency, decision, or blocker affects the plan.
For example, “Waiting for the design review; implementation is paused” tells teammates more than a stale In Progress status. A brief update can prevent unnecessary follow-up messages.
Use Fields Consistently
Agree on how your team uses priority, labels, and ticket types. If one person marks every task Urgent, priority stops helping people decide what to handle first.
Keep conventions easy to follow. A short team agreement can explain which ticket types to use and what details belong in a bug report.
ONES.com brings project management and knowledge management together in one platform. ONES Project is its project management product and a Jira alternative; ONES Wiki is its knowledge management product and a Confluence alternative. They are sold separately.

For teams reviewing ticket workflows, ONES Project offers Jira-compatible workflows, sprint management, custom workflows and fields, automation, and built-in reporting. Cloud and self-hosted deployments have full feature parity, with options for On-Premise, Private Cloud, and air-gapped environments.
Core Capabilities
- Teams need familiar issue tracking → ONES Project supports Jira-compatible workflows → teams can adapt familiar ways of organizing tickets.
- Generic workflows don’t match team steps → Custom workflows let teams define their process → work can move through stages that fit how the team operates.
- Standard fields miss important details → Custom fields capture project-specific information → teammates can track useful ticket context.
- Sprint planning feels disconnected from tickets → Sprint management connects planned work with the team’s cycle → progress is easier to review during a sprint.
- Manual handoffs consume time → Automation can handle selected workflow actions → teams can reduce repeated administrative steps.
- Progress is hard to see → Built-in reporting summarizes project activity → teams can review work without relying on extra reporting add-ons.
- Plugin dependence adds overhead → Native project management capabilities cover common workflow needs → teams may reduce the number of plugins required for those needs.
- Hosting requirements restrict deployment choices → Cloud, On-Premise, Private Cloud, and air-gapped deployments are available → teams can select an environment that fits their constraints.
Application Scenarios
A software team moving from Jira can assess whether its issue types, fields, and workflow stages map to ONES Project. Jira-compatible workflows can help preserve familiar practices during that evaluation.
A team with restricted network requirements can consider an air-gapped or other self-hosted deployment. Full feature parity between cloud and self-hosted versions means teams can compare deployment options without giving up product capabilities.
A project group that also needs a knowledge management space can consider ONES Wiki separately. ONES.com offers a free plan for up to 30 seats, which can give a team a practical way to evaluate its fit.
Common Challenges with Jira Tickets
Ticketing problems often come from unclear habits rather than a lack of fields. A team can make its queue more useful by agreeing on a few simple practices.
Tickets Have Vague Summaries
Problem: A title such as “Please check” tells the next person almost nothing.
Solution: Name the action or symptom, such as “Check why invoice totals change after editing.” Put background and reproduction details in the description.
Tickets Stay Open Without an Owner
Problem: A ticket may sit in a queue because nobody knows who should take the next step.
Solution: Assign a responsible teammate or route the ticket to a team queue with a clear handoff process. Revisit ownership when work moves between groups.
Statuses Don’t Match Reality
Problem: A ticket marked In Progress may actually be waiting for a review or outside decision.
Solution: Use the closest accurate workflow status and add a short comment describing the blocker. That gives teammates a clearer view of what can happen next.
Teams Create Duplicate Tickets
Problem: Two people report the same issue, and separate tickets begin collecting conflicting updates.
Solution: Search the project before creating a ticket, then link or close duplicates using the team’s agreed process. Keep useful details in the active ticket.
Frequently Asked Questions
Is a Jira ticket the same as a Jira issue?
Usually, yes. Jira commonly calls an individual work item an issue, while many teams call it a ticket in conversation. The item can represent a bug, story, task, or another configured type. If a team uses a specific definition for “ticket,” follow its local convention so everyone understands the terminology.
What is an example of a Jira ticket?
A bug ticket might be titled “Reset link expires before the email arrives.” Its description can explain how to reproduce the problem, what should happen, and what happens instead. A feature ticket could describe saving a delivery address at checkout, with acceptance criteria that explain how the team will verify the behavior.
Can I change a Jira ticket type?
In many Jira projects, a ticket type can be changed, though available options and permissions depend on project configuration. Changing type may affect fields, workflow behavior, or how the ticket appears in project views. Check the project’s process before converting a ticket, especially when it is already linked to other work.
What should I include when creating a Jira ticket?
Start with a clear summary and a description that gives enough context for someone else to act. For a bug, include reproduction steps and expected versus actual behavior. For a feature, explain the intended outcome and acceptance criteria. Add an owner, priority, or related ticket when those details help the team plan the work.
Conclusion
A Jira ticket is a trackable work item with a type, details, status, and other fields that help a team manage work. Stories, tasks, bugs, and epics describe different kinds of work, while workflow statuses show progress.
When tickets have vague summaries or missing ownership, work slows and teammates have to chase context. Clear descriptions, useful fields, and timely updates make each handoff easier to manage.
Start with one ticket: name the work clearly, add the details someone needs, and keep its status current. With those habits, Jira tickets become practical guides for the work ahead.