How to Create an Issue in Jira: Full 7-Step Process Guide
Need to create a clear Jira issue without missing key details? This 7-step jira create issue guide shows what to include. Read now to get started.
Need to report a bug or assign a piece of work in Jira, but the create screen has more fields than you expected? A rushed issue can land in the wrong project, leave teammates guessing, or disappear into an unhelpful queue.
That friction often comes from choosing the wrong issue type or leaving key details out. The good news: creating a useful Jira issue takes only a few minutes when you follow a clear sequence.
Here’s the truth: you don’t need to fill in every field. You do need to identify the work, explain what should happen, and give the right people enough context to act. This seven-step guide walks you through the process, from opening the create form to checking that your new issue is ready for the team.
Create an Issue in Jira: The Seven-Step Process
To create an issue in Jira, open the create form, select a project and issue type, add a clear summary, complete the useful fields, and submit. Then open the issue to confirm its details and status.
Here’s why: Jira’s fields and buttons can vary by project, permissions, and configuration. Use these seven steps as a reliable path, while following the labels you see on your screen.
-
Open the create form. Select Create in Jira’s top navigation. If you don’t see it, open the project and look for a create option in its issue or backlog view.
Some teams also enable keyboard shortcuts. If you already know your Jira setup, use your usual route; otherwise, the visible button is the simplest place to start.
-
Choose the project. Select the project where your team tracks this work. Check the project name carefully, especially if your organization has several projects with similar names.
For example, a login defect might belong in the product team’s project rather than the general operations project. The right project helps the issue reach the correct team and workflow.
-
Select an issue type. Common options include Bug, Task, Story, and Epic. Choose the type that best describes the work and matches your team’s conventions.
A broken checkout button is likely a bug. A request to add a new payment method may be a story or task, depending on how your team organizes product work.
-
Write a specific summary. Use a short title that explains the work or problem. Include the affected area and the action or result when possible.
“Checkout fails after applying a discount code” gives teammates more context than “Checkout issue.” Keep the summary focused; put the fuller explanation in the description.
-
Add a useful description and relevant fields. Explain what happened, what you expected to happen, and how someone can reproduce the problem. For a task, describe the requested outcome and any important constraints.
Complete required fields marked on the form. Depending on your project, you may also see priority, assignee, labels, components, due date, or sprint. Fill in details that help routing or planning.
-
Review before submitting. Check that the project, issue type, summary, and description make sense together. Confirm required fields are complete, and remove any accidental or confusing text.
If you have selected an assignee or sprint, make sure that choice fits the team’s workflow. You can often update these details later, but reviewing now can prevent avoidable handoffs.
-
Create the issue and verify it. Select Create to submit the form. Jira typically displays a confirmation or gives you a link to the new issue.
Open the issue and check its key, status, and visible details. If the issue is missing from the view you expected, check the project, filters, and permissions before creating it again.

What to Prepare Before Opening the Form
A little preparation makes issue creation faster and improves the handoff. Before you start, identify the project, the type of work, and the result you want the team to achieve.
For a bug report, note the steps that trigger the problem, what you expected, and what happened instead. For a request, describe who needs it and what a successful result looks like.
For example, “As a subscriber, I need to download my monthly invoice so I can submit it for reimbursement” gives a team more direction than “Add invoice download.” You might be wondering: do you need every detail first? No. Capture the essentials, then add useful context as it becomes available.
Where Else You Can Create an Issue
The top navigation is a convenient starting point, but Jira may also let you create issues from a project view, backlog, board, or another issue. The available options depend on your permissions and project configuration.
Creating an issue from a backlog can be helpful when you’re planning work with the team. Adding a related issue from an existing issue can make the connection clearer, such as linking a testing task to the feature it supports.
But here's the truth: the entry point doesn’t change the need for clear details. Whether you use a project screen or the main create form, check the selected project and issue type before submitting.
How to Write an Issue Teammates Can Act On
A good issue gives the next person a clear starting point. For a bug, include the steps to reproduce it, the expected behavior, the actual behavior, and any relevant device or browser details.
For planned work, describe the user need or business outcome, then clarify what should be included. For example, a task to “add a delivery date to order history” could specify which orders show the date and where it appears.
Keep the summary short and put supporting details in the description. If the issue needs a screenshot or another attachment, add it only when it helps explain the work and your project allows it.
How to Check and Manage a Newly Created Issue
After submission, confirm that Jira created the issue and assigned it the expected project key. Check the status, priority, assignee, and any links or labels that matter to your team.
If you can’t find the issue, start with the project you selected. A board may hide issues that don’t match its filters, and a project’s workflow may place new issues in a status that looks different from your usual queue.
When details change, update the issue rather than creating a duplicate. For example, if another teammate already reported the same checkout bug, link or comment on the existing issue according to your team’s process.
ONES.com brings project management and knowledge management together in one platform. ONES Project handles project work and offers a Jira alternative, while ONES Wiki provides a knowledge base as a Confluence alternative. The products are sold separately.

Creating a Jira issue is straightforward, but some teams also need structured workflows, reporting, and shared project knowledge. ONES.com may suit teams looking for those capabilities with cloud or self-hosted deployment options.
Core Capabilities
- Work tracked across disconnected processes: ONES Project supports Jira-compatible workflows → teams can use familiar issue-based processes within a different platform.
- Limited visibility into project progress: Built-in reporting gives teams views of work and progress → managers can review activity without relying on a collection of extra plugins.
- Workflows that don’t fit a team’s process: Custom workflows let teams shape issue movement → tasks can follow the stages their work actually requires.
- Fields that miss important context: Custom fields allow teams to capture relevant details → each issue can carry information suited to its project.
- Planning work across development cycles: Sprint management supports iteration planning → teams can organize work around planned sprints.
- Repeated actions that take time: Automation handles supported routine steps → teams can reduce manual work in common workflows.
- Requirements for running services on company infrastructure: ONES.com offers On-Premise and Private Cloud deployments → teams have options beyond the Cloud deployment.
- Restricted networks: An Air-gapped deployment is available → organizations can run the platform in an isolated environment.
ONES.com offers four deployment options: Cloud, On-Premise, Private Cloud, and Air-gapped. Its cloud and self-hosted versions have full feature parity, so self-hosting doesn’t mean giving up feature access.
The platform offers a free plan for up to 30 seats. Teams can also consider it when they want native project capabilities and fewer add-on plugins, particularly if on-premise deployment matters.
Application Scenarios
A software team can use ONES Project to track bugs, plan sprints, customize its workflow, and review progress through built-in reporting. It can keep the issue process familiar while adjusting fields to match the team’s needs.
An organization with restricted network requirements can evaluate an Air-gapped deployment. A team that wants project tracking alongside a knowledge base can consider ONES Project and ONES Wiki, which are available separately.
Common Challenges When Creating Jira Issues
The Create Button Is Missing
Your account may not have permission to create issues in that project, or the interface may place the option elsewhere. Open the project and check its issue view, then ask a project administrator to confirm your permissions if the option remains unavailable.
The Issue Type Doesn’t Match the Work
Choosing a bug for a feature request can send work through the wrong process. Check your team’s definitions, and ask a project lead when two types seem appropriate. The right type helps set expectations for fields and workflow.
The Issue Is Difficult to Find
A project board may show only issues that meet its filters. Confirm the project and issue key, then check another project view or search for the issue. Avoid creating it again until you know whether the first attempt succeeded.
Teammates Need More Information
A vague summary or description can lead to follow-up questions and delays. Add a concrete example, reproduction steps, or a clear expected result. If you don’t know a detail yet, say what remains uncertain rather than guessing.
FAQs About Creating Jira Issues
Can I create a Jira issue without choosing an assignee?
Often, yes. Whether an assignee is required depends on the project’s configuration and the fields shown in its create form. If the field is optional, you can leave it blank and let the team triage the issue. If your team expects issues to have owners, follow its assignment process or choose the appropriate teammate before submitting.
What is the difference between a task, a bug, and a story?
A bug describes a problem or unexpected behavior. A task is a piece of work that may not represent a user-facing feature. A story commonly describes a user need or product improvement. Jira projects can configure issue types differently, so check how your team defines each one before creating an issue.
Can I edit an issue after creating it?
In many Jira projects, you can open an issue and update fields such as its summary, description, priority, or assignee. Your permissions and workflow may limit which changes you can make. If a field is unavailable, ask a project administrator or follow your team’s process for requesting an update.
Why can’t I see the issue I just created?
First, check whether Jira confirmed creation and note the issue key if it appeared. Then verify the selected project and look for the issue in a broader project view or search. Boards can use filters that exclude some issues, and permissions may affect what you can see. Don’t submit a duplicate until you’ve checked whether the original exists.
Conclusion
Creating an issue in Jira comes down to seven practical steps: open the form, choose the project and type, write a clear summary, add useful context, review the fields, submit, and verify the result.
When issue creation feels confusing, slow down long enough to check the project and explain the work clearly. That small effort can prevent misrouted tasks and unnecessary follow-up. If your team needs broader workflow, reporting, or deployment options, ONES.com is another platform to evaluate alongside Jira.