Create an Issue in Jira: A Step-by-Step Guide for Teams

Not sure how to create issue in Jira with enough detail? Follow this step-by-step guide to create actionable issues and avoid delays. Read now to get started.

To create an issue in Jira, open the project, select Create, fill in the required fields, and submit it. The challenge is making sure your issue has enough detail for someone else to act on it.

A vague summary or missing acceptance criteria can lead to delays, repeated questions, and work that misses the mark. Even a simple task may stall if it lands in the wrong project or has no clear owner. But here's the truth: a reliable issue starts with a few deliberate choices. I’ll walk you through the steps, explain what to include, and show you how to check that your new issue is ready for the team.

How to Create an Issue in Jira

Follow these steps to create a Jira issue. Field names and available options can vary by project configuration, issue type, and your permissions.

Open the correct project

Sign in to Jira and navigate to the project where the work belongs. Check the project name before continuing; issues created in the wrong project may follow different workflows or be invisible to the intended team.
Choose Create

Select the Create button, often available in the top navigation. If your Jira layout differs, look for an equivalent create option within the project. You may need permission to create issues in that project.
Select an issue type

Choose the type that best describes the work, such as a task, bug, story, or epic. For example, a broken password reset is usually a bug, while a request to add a new reset flow may be a story.
Write a clear summary

Use a short title that explains the work or problem. “Fix login error on Safari” gives a teammate more context than “Login issue.” Keep the summary focused so it remains easy to scan in a backlog.
Add a useful description

Explain what needs to happen and why. For a bug, describe the expected result, the actual result, and the steps that reproduce it. For a feature, state the user need and what a successful outcome looks like.
Complete relevant fields

Add an assignee, priority, labels, components, due date, or sprint when those fields apply. Some fields are required, while others may be hidden or specific to your project. If a required field is unclear, check with your project administrator rather than guessing.
Review and submit

Check the project, issue type, summary, description, and any required fields. Then select Create in the form. Jira should confirm that the issue was created and may display its issue key, such as APP-214.
Confirm the issue is ready for work

Open the new issue and review its status, assignee, and project details. If the issue belongs in a sprint or a particular workflow stage, update it according to your team’s process.

Choose the Right Issue Type and Project

Issue type affects how a piece of work is tracked, grouped, and completed. A bug usually records unexpected behavior, while a task captures work that does not fit a user story. An epic groups larger efforts that may contain multiple stories or tasks.

For example, “Add a filter to the reports page” could be a story if it delivers a user-facing capability. “Update the test environment” may be a task. Your team’s conventions matter, so check a similar issue when you are unsure.

Here's why: selecting the right project and type at the start can prevent issues from landing in the wrong backlog or following an unsuitable workflow. If you cannot see the project or type you need, permissions or project settings may need attention.

Write an Issue Teammates Can Act On

A useful issue tells a teammate what is happening, who it affects, and what outcome is expected. You do not need a long description for every task, but you do need enough detail to avoid guesswork.

For a bug, try this example: “On Safari 17, selecting ‘Reset password’ returns a blank page. Expected: the reset form appears. Steps: open the sign-in page, select ‘Reset password,’ and observe the result.” That gives a developer a practical place to start.

For a feature, describe the need and how the team can recognize completion. “As a project lead, I want to filter reports by owner so I can review each person’s open work” is clearer than “Improve reports.” Add acceptance criteria when several outcomes must be checked.

Set Ownership, Priority, and Planning Details

An assignee makes ownership visible, but assigning work to the wrong person can create an unnecessary handoff. If you do not know who should own an issue, ask the team or leave it unassigned when your process permits.

Use priority to communicate urgency, not personal preference. A service outage affecting every customer deserves different attention from a minor visual adjustment. Labels and components can also help teams group related work, as long as the terms are used consistently.

You might be wondering: should every issue go into a sprint immediately? Not necessarily. Teams often refine and estimate work before sprint planning. Add a sprint only when the issue is ready and your team’s process calls for it.

After You Create an Issue: Review and Track It

Issue creation is the beginning of a work item’s lifecycle. Check that the issue appears in the expected project view, and confirm its status and ownership. If your team uses a board, make sure the issue appears in the appropriate backlog or column.

If the issue is missing, first check the project and any active filters. A board may hide issues that do not match its configuration. If you cannot edit a field or move an issue, ask a project administrator to check permissions and workflow rules.

The best part? A short review can catch problems before work starts. For instance, noticing that a bug has no reproduction steps early can save a teammate from spending time trying to recreate it.

A Related Issue-Management Option: ONES.com

ONES.com brings project management and knowledge management together on one platform. ONES Project is its project management product and a Jira alternative; ONES Wiki is its knowledge base product and a Confluence alternative. They are sold separately, so teams can choose the product that fits their needs.

ONES.com product screenshot

For teams comparing issue workflows, ONES Project offers Jira-compatible workflows, custom workflows and fields, sprint management, automation, and built-in reporting. Its capabilities can help teams manage issue creation and follow-up while reducing reliance on extra plugins. Teams can use cloud or self-hosted deployments, including on-premise, private cloud, and air-gapped options.

Core capabilities for issue-based work

Issue tracking: When work is scattered across several processes, ONES Project provides project tracking so teams can manage tasks and progress in one place.
Jira-compatible workflows: When a team needs familiar workflow patterns, compatible workflows help support a transition without rebuilding every process from scratch.
Custom workflows: When work requires different approval or delivery stages, teams can configure workflows to match their process and make responsibilities clearer.
Custom fields: When a standard issue form misses important details, custom fields capture the information relevant to that team’s work.
Sprint management: When teams plan work in iterations, sprint features help organize issues and follow planned work through delivery.
Automation: When routine updates take time, automation can handle selected workflow actions and reduce manual steps.
Built-in reporting: When teams need visibility into progress, built-in reports help them review project activity without relying on as many additional plugins.
Deployment choice: When hosting requirements differ, Cloud, On-Premise, Private Cloud, and Air-gapped deployments give teams distinct ways to run the platform.

Where it may fit

A software team moving from Jira could use ONES Project to manage bugs, stories, sprints, and custom workflow stages. A team with strict network requirements could evaluate an on-premise or air-gapped deployment while maintaining the same feature set as the cloud version.

ONES.com also offers a free plan for up to 30 seats. Teams can use ONES Project for project management and choose ONES Wiki separately if they also need a knowledge base. This setup can suit teams that want to assess issue management first, then decide whether a separate knowledge management product is useful.

Common Challenges When Creating Jira Issues

The issue is in the wrong project: Confirm the project before submitting. If you discover the mistake afterward, follow your team’s process for moving or recreating the issue.
The form requires a field you do not understand: Required fields can vary by project and issue type. Ask an administrator or teammate what the field means before entering a guess.
The issue has too little detail: Add expected behavior, reproduction steps, or acceptance criteria. A concrete example often answers questions that a broad description leaves open.
The issue does not appear on the board: Check the board’s filters, project, and status settings. If the issue still does not show, ask a project administrator to review the board configuration.

Frequently Asked Questions

Can I create an issue in Jira without assigning it?

Often, yes. Whether you can leave an issue unassigned depends on project settings and team conventions. If the work is not yet ready for an owner, leaving it unassigned may be appropriate. If your team requires an assignee, ask who should take responsibility rather than choosing someone at random.

Why can’t I see the Create button in Jira?

The button’s location can vary with the Jira interface, and your account may not have permission to create issues in the project. Try opening the project directly and checking its available actions. If you still cannot create an issue, ask a project administrator to review your permissions.

What should I include in a Jira bug report?

Include a specific summary, the affected area, steps to reproduce the problem, the expected result, and what actually happened. Add relevant context such as the browser or device when it helps someone reproduce the issue. For example, “Checkout shows a blank page in Safari 17 after selecting Pay” is more actionable than “Checkout is broken.”

Can I change an issue after creating it?

Usually, you can edit fields such as the summary, description, assignee, or priority, provided you have permission. Some changes may be restricted by workflow rules or project configuration. Open the issue and use its available edit controls; if a field cannot be changed, contact a project administrator.

Conclusion

Creating a useful Jira issue means choosing the right project and type, writing a clear summary, adding actionable details, and checking ownership and planning fields. A quick review after submission helps catch missing information before work begins.

When vague issues are slowing your team down, a consistent creation process can reduce confusion and improve handoffs. Start with the essentials, add context that helps someone act, and follow the workflow your team has agreed on. For teams assessing a different issue-management setup, ONES Project offers another way to manage work, with deployment options that include self-hosted environments.