How to Create a Jira Ticket: 7 Quick Steps With Examples
Need to know how to create ticket in Jira? Follow 7 quick steps with examples to write clear, actionable tickets. Click to learn more.
A Jira ticket can take only a few minutes to create, yet a poorly written one can leave your team guessing about the work. Missing details lead to follow-up questions, incorrect priorities, and tasks that stall before anyone starts. If you’re learning how to create a ticket in Jira, a clear process helps you capture the request and give the right person enough context to act. But here’s the truth: choosing “Create” is the easy part. The useful work happens when you select the right project and issue type, describe the outcome, and complete the fields your team relies on. Follow these seven steps to create a well-structured Jira ticket, with practical examples you can adapt for bugs, tasks, and user stories.
How to Create a Ticket in Jira: 7 Steps
A Jira ticket, also called an issue, records a piece of work in a project. To create one, open the right project, choose the appropriate issue type, complete the necessary details, and submit it. These steps work as a general guide; your Jira administrator may customize available fields and workflows.

1. Open the correct Jira project
Start in the Jira project where the work belongs. Select the project from the project menu or navigate to its board, then confirm its name before creating an issue.
For example, a checkout bug belongs in the team’s storefront project, while a request to update employee onboarding belongs in the internal operations project. Choosing the right project helps route the ticket to the people responsible for that work.
2. Select Create
Choose Create in Jira’s navigation. A form will appear with fields for the project, issue type, summary, and other details. The exact layout can vary by Jira version and project configuration.
If the form opens with the wrong project selected, change it before continuing. Some fields depend on the project or issue type, so checking this first can save you from entering details twice.
3. Choose the issue type
Pick the issue type that best describes the work. Common options include Bug, Task, Story, and Epic, though names and availability vary between teams.
For example, use a bug for a repeatable problem, such as a payment button that does nothing. Use a task for planned work, such as updating a help page. A user story usually describes a capability from a person’s perspective.
When you’re unsure, check the project’s conventions or ask the project lead. The right issue type can determine which fields appear and how the ticket moves through the workflow.
4. Write a specific summary
Use the summary to state the main problem or outcome in a few words. A helpful summary is specific enough to understand in a work queue without opening the ticket.
Vague: “Checkout issue”
Clearer: “Payment button stays inactive after valid card details are entered”
For planned work, describe the action and the area it affects. “Add a delivery estimate to the order confirmation page” gives more direction than “Delivery update.”
5. Add a useful description
Explain what needs attention and include the context someone would need to take the next step. For a bug, describe what happened, what you expected, and how to reproduce the problem. For a task, state the requested result and any relevant constraints.
For example: “On the staging checkout page, enter a valid card number and select Pay. The button remains disabled. It should become active after all required fields are complete.” This gives a teammate a starting point for investigation.
6. Complete relevant fields and add context
Fill in fields your team uses, such as priority, assignee, labels, components, due date, or sprint. Required fields often have an asterisk. If you don’t know a value, follow your team’s process rather than guessing.
Add useful context through links, attachments, or comments when the project allows them. For instance, a screenshot can help explain a visual defect, while a link to a related issue can show earlier investigation.
Here’s why: carefully selected details can help the right teammate assess urgency and scope. Extra fields that add no value can make the ticket harder to scan, so focus on information that affects the work.
7. Review and create the ticket
Before submitting, check that the project, issue type, summary, and description are correct. Confirm that any required fields are complete and that your example steps do not include private or sensitive information.
Select Create to submit the form. Jira should display a confirmation or show the new issue. Open it, check that the details appear correctly, and share its issue key with relevant teammates.
What to Include in a Strong Jira Ticket
A useful ticket answers three questions: what is happening, why it matters, and what someone can do next. For a bug, include reproduction steps and the expected result. For a task, explain the intended outcome and any conditions the team must meet.
Consider a customer who cannot reset a password. “Reset problem” leaves the team with little to investigate. “Password reset link expires immediately for accounts created today” identifies the affected action and condition.
The best part? You don’t need a long description when the details are clear. A short, precise ticket can be more useful than a page of background that hides the important facts.
Example ticket fields
| Field | Example | Why it helps |
| Issue type | Bug | Shows the kind of work being reported. |
| Summary | Reset link expires immediately for new accounts | Identifies the issue in the project queue. |
| Description | Steps to reproduce, expected behavior, and actual behavior | Gives a teammate a practical way to investigate. |
| Priority | High, if the project’s criteria support it | Helps the team assess urgency consistently. |
| Assignee | The responsible teammate, if known | Clarifies ownership without guessing. |
Field labels and priority options can differ between Jira projects. Follow your team’s definitions, especially when assigning urgency or ownership.
Examples for Bugs, Tasks, and Stories
For a bug ticket, describe the conditions that cause the failure. Include a short sequence of steps, the result you observed, and what should happen instead. “The app crashes” is difficult to reproduce; “The app closes after selecting Save on the profile screen with no phone number entered” is more actionable.
For a task, describe the deliverable. “Review the onboarding email for outdated links and update the approved copy” makes the work and finish line clear. If the task depends on another team or approval, mention that constraint in the description.
For a story, explain who needs the capability and why. For example: “As a shopper, I want to see the delivery estimate before payment so I can choose an appropriate shipping option.” The team can then clarify acceptance criteria before implementation.
Let me explain: these examples provide a starting point, not a rigid formula. A small internal request may need only a summary and a few sentences. A defect affecting payments may need more context and evidence.
After You Create the Jira Issue
Creating a ticket starts the work; it doesn’t guarantee that the ticket is ready for action. Check whether it appears in the expected project view and whether its status matches your team’s workflow. Some projects place new issues in a backlog, while others move them into a triage queue.
If a teammate needs to respond, add a comment that explains what you need and when. If the work relates to another issue, link the two when that feature is available. For example, a bug fix can be connected to the release task that will include it.
You might be wondering: should you assign every ticket immediately? Assign it when you know the responsible person and your team expects that. Otherwise, leaving it unassigned for triage may prevent incorrect ownership from slowing down the request.
ONES.com is a unified platform for project management and knowledge management, with ONES Project for project work and ONES Wiki for knowledge management. They are sold separately, so teams can choose the capabilities they need.

For teams reviewing options beyond Jira, ONES Project is a Jira alternative with Jira-compatible workflows, built-in reporting, custom workflows and fields, sprint management, and automation. Its available deployment choices include Cloud, On-Premise, Private Cloud, and air-gapped environments.
Core capabilities
- Jira transition concerns: Jira-compatible workflows help teams carry familiar work patterns into ONES Project, reducing the need to rebuild every process from scratch.
- Too many add-ons: Built-in reporting and automation can cover common project needs, helping teams reduce plugin dependency.
- Rigid issue fields: Custom fields let teams capture details that matter to their work, so tickets can include relevant context.
- Workflow changes require workarounds: Custom workflows let teams shape issue movement around their approval and delivery steps.
- Sprint planning is disconnected: Sprint management supports planning and tracking work within a team’s delivery cycle.
- Progress is difficult to follow: Built-in reporting gives teams a way to review project activity and status.
- Hosting requirements are strict: On-premise, private cloud, and air-gapped deployment options support different infrastructure needs.
- Teams need related knowledge management: ONES Wiki provides a knowledge management option alongside ONES Project, while remaining separately sold.
ONES.com offers a free plan for up to 30 seats. Its cloud and self-hosted versions have feature parity, giving teams a choice of hosting without losing feature access solely because of deployment type.
Application scenarios
A software team moving from Jira: A team can assess ONES Project’s Jira-compatible workflows, custom fields, and sprint management against its existing process. It can test whether the setup supports issue tracking without relying on as many plugins.
A team with restricted hosting requirements: An organization that cannot use a public cloud service can evaluate On-Premise, Private Cloud, or air-gapped deployment. It can keep project management within its approved environment while using the same feature set available in the cloud version.
Common Challenges When Creating Jira Tickets
- The ticket is too vague. Add the affected area, observed behavior, and a concrete example. For a bug, include steps someone can repeat.
- The wrong issue type or project is selected. Confirm both before submitting. If the ticket is already created, follow your project’s process for moving or correcting it.
- Priority is based on guesswork. Use your team’s priority criteria, such as customer impact or blocked work. Ask for triage when the severity is unclear.
- The ticket has too many unrelated details. Keep the description focused on the requested work. Link related issues when possible instead of mixing separate tasks into one ticket.
These problems are easier to prevent with a brief review before submission. A quick check can catch a mismatched project or a missing reproduction step before the ticket enters the team’s queue.
Frequently Asked Questions
What is a Jira ticket?
A Jira ticket is a record of work in a Jira project. Jira also calls it an issue. Depending on the project, it can represent a bug, task, story, epic, or another configured type of work. A ticket usually has a summary and may include a description, status, priority, assignee, and other fields. Teams use these records to organize and follow work through a workflow.
Can I create a Jira ticket without assigning it?
Yes, if your project allows tickets to remain unassigned. Some teams create issues first and assign them during triage; others expect the creator to select an owner. Check your project’s workflow and team conventions. If you don’t know who should take the work, leaving the assignee blank may be better than choosing someone at random.
What should I write in a Jira bug description?
Describe the problem, the steps that trigger it, what you expected, and what actually happened. Include relevant conditions, such as the page, device, or account state, when they help reproduce the issue. For example, explain which button you selected and what appeared afterward. Add a screenshot or link only when it provides useful context and your project permits it.
Can I edit a Jira ticket after creating it?
Often, yes. Open the issue and use its available edit controls to update fields or clarify the description. Your permissions and project configuration determine which changes you can make. If the issue has moved through review or delivery, add a comment explaining a significant change so teammates understand why the ticket’s scope or priority shifted.
Conclusion
Creating a useful Jira ticket means choosing the right project and issue type, writing a clear summary, adding enough context, and checking the details before submission. The seven steps give you a repeatable way to create bugs, tasks, and stories that teammates can understand.
If your tickets keep generating clarification questions, improve the description with concrete steps and expected outcomes. If your team is evaluating a Jira alternative, compare its workflow, deployment, and reporting needs with options such as ONES Project. A clear ticket gives the work a better starting point and helps your team decide what to do next.