How to Create a Jira Issue: A Simple Step-by-Step Guide

Creating a Jira issue sounds simple until your team opens one with a vague summary, missing details, and no clear owner. Then the ticket creates more questions than progress. A small mistake at creation can cause delays, duplicate work, and endless comments asking what should happen next.

That frustration grows when you are new to Jira. You may wonder which issue type to choose, where to add acceptance criteria, or how to set the right priority. You might even create a ticket successfully and still give your team too little information to act.

But here's the truth: creating a useful Jira issue takes only a few deliberate steps. This guide shows you exactly how to create one, what each field means, and how to write issues your team can understand and complete.

How to Create a Jira Issue Step by Step

To create a Jira issue, select Create, choose the project and issue type, add a clear summary and description, complete the important fields, then select Create. The exact screen may differ slightly between Jira Cloud and Jira Data Center, but the workflow stays similar.

1. Open the Create issue window. Select Create in the top navigation bar. You can also use the keyboard shortcut configured by your Jira administrator.
2. Choose the project. Select the project where your team will track and resolve the work. Check the project name carefully before continuing.
3. Select an issue type. Choose Story, Task, Bug, Epic, or another type configured for your project. Pick the type that best describes the work.
4. Write a specific summary. Describe the result or problem in one short sentence. For example, use “Add password reset confirmation email” instead of “Email problem.”
5. Add the description. Explain the context, expected result, steps to reproduce, requirements, or useful links. Give the person handling the work enough detail to begin.
6. Set the priority. Choose a priority that reflects impact and urgency. Avoid marking every request as highest priority.
7. Assign the issue. Select a responsible person when you already know who should handle it. Otherwise, leave it unassigned if your team uses a triage process.
8. Add labels, components, or a sprint. Use these fields only when they help your team filter, organize, or plan the work.
9. Attach supporting material. Add screenshots, error messages, recordings, or other relevant items when they help explain the issue.
10. Review and create the issue. Check the project, issue type, summary, priority, and owner. Select Create when the details are accurate.

Using the Create Button

The fastest route is the Create button at the top of Jira. After selecting it, Jira opens a form containing fields controlled by your project configuration.

You may see different fields across projects. A software project might request an environment, affected version, and sprint. A marketing project might show campaign, target date, and approval fields instead.

Choosing the Right Issue Type

Issue types help your team understand the kind of work involved. A Bug usually describes behavior that does not work as expected. A Task covers a defined piece of work, such as updating a deployment script.

A Story often represents a user-focused requirement. An Epic groups several related issues under a larger outcome, such as launching a new billing system.

Issue type	Useful example
Bug	Checkout page displays a blank screen after payment
Task	Update the staging environment variables
Story	Allow customers to save multiple shipping addresses
Epic	Launch the redesigned account experience

Writing the Summary

Your summary should tell someone what the issue concerns without requiring them to open it. Keep it specific, concise, and focused on one outcome.

Compare these examples:

• Weak: Login issue
• Stronger: Reset password link returns a 404 error
• Weak: Improve dashboard
• Stronger: Add weekly revenue filter to the sales dashboard

A useful summary helps with search results, sprint planning, notifications, and reports. It also makes the issue easier to recognize months later.

Adding a Useful Description

The description should explain what happened, what should happen, and what someone can do to verify the result. Use headings or short sections when the issue contains several details.

For a bug, include the steps that reproduce the behavior. For a feature, describe the user outcome and the conditions that define completion.

A simple bug description might look like this:

• Steps to reproduce: Open the checkout page, enter a valid card, and select Pay.
• Expected result: The order confirmation page appears.
• Actual result: The page becomes blank and the order remains pending.
• Environment: Chrome on macOS, production site.

What to Include in a High-Quality Jira Issue

The best Jira issue gives a teammate enough context to act without scheduling a separate meeting. That does not mean writing a long essay. It means including the details that affect the decision or the work.

Here's why: missing context creates hidden work. A developer may spend an hour reproducing a problem that could have been explained in two sentences.

A Clear Outcome

State what should change when the issue is complete. “Improve performance” is difficult to assess because nobody knows which measure matters.

“Reduce the product search response time to under two seconds for common queries” gives the team a clearer target. It connects the work to an observable result.

Acceptance Criteria

Acceptance criteria describe the conditions that must be true before the issue is complete. They reduce disagreements during review and testing.

For example, a story for saved shipping addresses could include:

• Customers can add a new shipping address during checkout.
• Customers can select a saved address for a later purchase.
• Customers can remove an address from their account.
• The checkout page shows validation errors for missing required fields.

Each criterion gives the team a practical way to check progress. It also helps testers focus on the intended behavior.

Relevant Context

Add information that changes how the issue should be handled. This could include a customer example, a related issue key, a design link, an error message, or a deadline connected to a launch.

Avoid adding unrelated history. If a detail does not help someone understand, complete, or verify the work, leave it out or place it in a comment.

How Jira Fields Affect Planning and Tracking

Jira fields are not merely administrative details. They help teams group work, identify ownership, measure progress, and decide what deserves attention first.

You might be wondering: which fields deserve the most attention? Start with the project, issue type, summary, description, priority, and assignee. Add other fields when your team has a clear reason to use them.

Priority

Priority should reflect business impact and urgency. A production outage that prevents customers from completing orders deserves more attention than a minor spacing issue in a rarely visited screen.

Consider both factors together. A problem can have high impact but low urgency if a temporary workaround exists. A deadline-sensitive request can be urgent even when its overall impact is moderate.

Assignee

The assignee indicates who owns the next action. Assign an issue to a person only when that ownership is clear.

If your team reviews new work during triage, leaving the issue unassigned may be appropriate. The important point is to follow one consistent team rule.

Labels and Components

Labels and components can improve filtering, but uncontrolled use creates clutter. Agree on naming conventions before creating dozens of variations such as checkout, Checkout, and checkout-flow.

Components often work well for stable areas of a product. Labels are more flexible and may suit temporary themes, release groups, or cross-team initiatives.

Parent Issues, Links, and Subtasks

Use relationships when they clarify how work connects. A story can belong to an epic, while a task can block another task.

For example, a mobile release might include an epic for the launch, stories for each customer capability, and subtasks for design, engineering, and testing. This structure shows the bigger picture without placing every detail in one issue.

Creating Jira Issues for Different Types of Work

The right issue format depends on what you are tracking. A bug needs reproducible behavior. A feature needs a user outcome. A task needs a clear action and completion condition.

The best part? You can use a small template for each type and still keep every issue easy to scan.

Bug Report Example

A useful bug report answers four questions: what happened, where it happened, how to reproduce it, and what should have happened instead.

Example summary: Search results disappear after applying the price filter.

Example description:

• Steps: Search for “running shoes,” open Filters, select a price range, and apply it.
• Expected: Matching products remain visible.
• Actual: The results area shows no products until the page reloads.
• Impact: Customers cannot narrow search results on mobile devices.

Feature Request Example

A feature issue should explain who needs the capability and why it matters. This keeps the team focused on the outcome rather than a vague list of requested functions.

Example summary: Let account owners export monthly usage reports.

Example acceptance criteria:

• Account owners can select a month from the reporting screen.
• The export includes usage totals and service names.
• The system shows a clear message when no usage exists.
• Only authorized account owners can export the report.

Task Example

A task usually describes a concrete action that supports a larger goal. Include the expected result so another person can confirm completion.

Example summary: Configure monitoring alerts for payment failures.

The description could specify which service requires monitoring, which thresholds matter, who receives alerts, and how the team will test the setup.

Using ONES for Workflows Around Jira Issues

Jira is useful for issue tracking, while broader work may involve approvals, forms, planning, collaboration, and cross-team coordination. ONES can support those surrounding workflows when your team needs more than issue creation alone.

Let me explain: the right workflow matters as much as the ticket itself. A well-written Jira issue can still stall when approvals, handoffs, and ownership remain unclear.

Capabilities That Support Project Work

• Project planning: Organize initiatives, milestones, and delivery goals in one workspace.
• Task management: Assign work, set due dates, track progress, and clarify ownership.
• Custom workflows: Build approval and handoff stages that match how your team operates.
• Team collaboration: Keep discussions, decisions, and updates connected to the relevant work.
• Progress reporting: Use dashboards and status views to identify delays early.
• Permission controls: Limit access to sensitive projects and manage responsibility by role.
• Cross-functional coordination: Connect marketing, product, engineering, and operations work.
• Reusable templates: Standardize recurring requests, launches, reviews, and internal processes.

For example, a product team could use Jira for engineering issues and ONES for a launch workflow involving product approval, marketing review, legal checks, and release coordination.

That setup can reduce scattered communication because each team sees the work that affects its responsibilities. Choose the arrangement that fits your existing process rather than adding another platform without a clear purpose.

Common Mistakes When Creating a Jira Issue

Using a Vague Summary

Problem: A summary such as “Fix checkout” does not explain the actual problem or desired result.

Solution: Mention the affected area and behavior. “Checkout confirmation page fails after Apple Pay payment” gives immediate context.

Leaving the Description Empty

Problem: The assignee must contact the creator before starting work.

Solution: Add the goal, relevant context, expected behavior, and any steps needed to reproduce the issue.

Choosing the Wrong Project

Problem: The issue appears on the wrong board, misses the intended workflow, or becomes difficult for the responsible team to find.

Solution: Verify the project before completing the form. If the project is unclear, ask the project administrator or triage group.

Marking Everything as Urgent

Problem: When every issue has high priority, priority stops helping the team make decisions.

Solution: Explain the impact and deadline. Reserve the highest levels for work that genuinely needs immediate attention.

Adding Too Many Labels

Problem: Inconsistent labels create noisy filters and unreliable reports.

Solution: Use established labels and remove unnecessary variations. A short shared naming guide can prevent repeated cleanup.

Common Challenges

The Create Button Is Missing

Problem: You cannot see the Create button or cannot select a particular project.

Solution: Your Jira permissions may not allow issue creation in that project. Contact the project administrator and ask for the required permission.

The Issue Type You Need Is Unavailable

Problem: The project does not offer Bug, Story, Task, or another type you expected.

Solution: The project may use a customized issue type scheme. Choose the closest approved type, or ask an administrator to confirm the correct workflow.

You Are Unsure Who Should Own the Work

Problem: Assigning the wrong person can delay triage and create confusion.

Solution: Leave the issue unassigned when your team has a review queue. Add the responsible team or component if those fields are available.

The Description Has Too Much Detail

Problem: A long description hides the key requirement beneath unrelated history.

Solution: Put the goal, expected result, and immediate context first. Move optional background into a separate section or comment.

FAQs

Can I create a Jira issue without assigning it?

Yes. Many teams leave new issues unassigned until a triage meeting or queue review. This approach works when someone regularly checks unassigned work and decides ownership. If your team expects every issue to have an owner immediately, assign the person responsible for the next action. Avoid assigning an issue randomly just to remove the unassigned status.

What is the difference between a Jira task and a story?

A task usually describes a specific piece of work, such as configuring alerts or updating a deployment process. A story usually describes a capability or outcome for a user, such as allowing customers to save payment methods. Your team may define these types differently, so check its project guidelines. Consistent usage matters more than the label itself.

How detailed should a Jira issue description be?

Include enough detail for the assignee to understand the goal and begin work without repeated clarification. A bug usually needs reproduction steps, expected behavior, actual behavior, and environment details. A feature usually needs the user outcome, requirements, and acceptance criteria. Keep unrelated history out of the main description so the important information remains easy to find.

Can I edit a Jira issue after creating it?

Yes, if your permissions allow editing. You can usually update the summary, description, priority, assignee, labels, and other fields. Add a comment when the change represents a new decision or important clarification. For major requirement changes, consider discussing whether a new issue would provide cleaner tracking.

How do I create a Jira issue from another issue?

Open the existing issue and use the available option for creating a linked issue, subtask, or related work item. The exact menu label depends on your Jira configuration. Choose a subtask when the work belongs directly to the current issue. Choose a linked issue when both items need separate ownership or separate progress tracking.

Conclusion

Creating a Jira issue is straightforward: choose the right project and type, write a specific summary, explain the work clearly, add useful fields, and review everything before submitting.

The real challenge is avoiding vague tickets that slow down the team. A clear outcome, practical acceptance criteria, and relevant context can turn a basic issue into an actionable work item.

But here's the truth: you do not need a complicated template. Start with the result, explain what matters, and give the next person enough information to act. That simple habit makes Jira easier to search, prioritize, assign, and complete.