How to Create an Issue in Jira: 7 Clear Steps to Follow
Struggling with vague tickets? Learn how to create an issue in Jira in 7 clear steps, with the right type and details. Read now.
A Jira issue can be a task, bug, story, or another piece of work, but choosing the wrong type or skipping key details can slow everyone down. A vague issue may lead to follow-up questions, missed work, or a ticket nobody knows how to finish. To create an issue in Jira, open the right project, select Create, choose an issue type, add a clear summary and useful details, then submit it. I’ll walk you through seven practical steps, including what to check before and after you create the ticket. But here’s the truth: a well-written issue is more than a saved form. It gives your team enough context to act without guesswork.
How to Create an Issue in Jira: 7 Steps
-

1. Open the correct Jira project
Start in the project where the work belongs. Jira projects can have different teams, permissions, workflows, and issue types, so selecting the right one helps the ticket reach the people who need to handle it.
If your team has several projects, check the project name and key before moving on. For example, a checkout bug should usually go into the product team’s project, not a general operations queue.
-
2. Select Create
Choose Create in the Jira navigation. Depending on your Jira setup and screen size, the button’s position may vary. The create-issue window should show the project and fields needed for a new ticket.
If you do not see the option, you may lack permission to create issues in that project. Ask a project administrator to check your access rather than creating the ticket in an unrelated project.
-
3. Choose the issue type
Pick the type that best describes the work. Common options include a task, bug, story, epic, and sub-task, though each project can use its own configuration.
A login failure is usually a bug. A request to add a password reset option may be a story or task. If you are unsure, check your team’s conventions because issue type can affect workflow, reporting, and required fields.
-
4. Write a specific summary
Use the summary to say what needs attention in a few words. A useful summary is specific enough to make sense in a board or search result without opening the issue.
For example, “Fix login” gives little context. “Show an error when a user enters an expired password reset link” describes the problem more clearly and helps teammates recognize the work.
-
5. Add a description and useful details
Explain the problem or requested work in the description. For a bug, include what happened, what you expected, and the steps to reproduce it. For a task, describe the intended result and any relevant constraints.
Fill in relevant fields such as priority, assignee, labels, components, due date, or sprint if your team uses them. Avoid guessing at values you do not know. A wrongly assigned owner or priority can create more work than leaving an optional field blank.
-
6. Review and submit the issue
Before you select Create, check the project, issue type, summary, description, and required fields. Confirm that the ticket describes one piece of work and gives its owner enough context to start.
Some Jira projects require extra fields or use custom forms. If Jira flags a missing value, complete the required field and review the rest of the form before submitting again.
-
7. Confirm the ticket and add follow-up details
After submission, open the new issue and check that its key, status, and details look right. Jira commonly assigns a unique issue key, such as TEAM-123, that teammates can use to find or discuss the ticket.
Add a comment if you need to clarify something, link a related issue when useful, or update the assignee if the work has a clear owner. A quick final check helps catch mistakes while they are easy to correct.
Before You Create a Ticket, Gather the Essentials
A little preparation can make the create form much easier to complete. Before opening it, identify the project, the kind of work, the desired outcome, and any details someone will need to get started.
For a bug, you might note the affected page, the steps that trigger the problem, and what you expected to happen. For a task, describe the finished result. “Update the onboarding screen so new accounts see the current setup steps” is more actionable than “Improve onboarding.”
You might be wondering: do you need to complete every field? Usually, no. Fill in required fields and the optional details that help your team prioritize, assign, or complete the work. A short, relevant ticket is more useful than one packed with uncertain guesses.
Choose an Issue Type That Matches the Work
Issue types help a team distinguish kinds of work and report on them. The available types depend on how the Jira project is configured, so one team’s list may differ from another’s.
- Bug: Something is broken or behaving differently from what the team expects.
- Task: A specific piece of work needs to be completed.
- Story: A change or capability is described from the perspective of someone who needs it.
- Epic: A larger body of work that can be divided into related issues.
- Sub-task: A smaller piece of work connected to a parent issue.
For example, a team could create an epic for improving account security, then add separate stories or tasks for password reset, login alerts, and recovery options. If an existing issue type does not fit, ask your project lead before creating several tickets with a misleading type.
Write Issue Details That Help Someone Take Action
A good issue description answers the questions a teammate is likely to ask first. Keep it focused on the work, and use headings or short lists when several details need to be scanned quickly.
For a bug, include the steps to reproduce it, the result you saw, and the result you expected. For example: “Open account settings, choose Change email, and save a valid address. The page displays a success message, but the account still shows the old address.” That gives a teammate something concrete to investigate.
For a feature or task, state the outcome and any acceptance criteria. “The save button is disabled until all required fields are complete” gives a clearer finish line than “Make the form better.” Add only details that help the owner understand or verify the work.
After Creation: Keep the Issue Useful
Creating the ticket is the start of its life in Jira. Once it exists, keep its status, owner, and discussion current as the work changes. If the request is no longer needed, follow your team’s process for closing or canceling it.
Link related work when it helps explain a dependency or shared goal. For example, a new checkout feature may depend on a separate payment service change. A link makes that relationship easier to see than a mention buried in a long comment.
When a ticket grows beyond one clear outcome, discuss whether to split it into smaller issues. A ticket that combines a login bug, a design update, and a reporting change can be difficult to assign and track. Smaller, connected issues often make progress and ownership clearer.
A Project Management Alternative: ONES.com
ONES.com brings project management and knowledge management together in a unified 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, so teams can choose what they need.

If your team manages issues in Jira, ONES Project offers Jira-compatible workflows, sprint management, custom workflows and fields, automation, and built-in reporting. Its Cloud and self-hosted deployments have full feature parity, giving teams deployment choices without splitting the feature set. The platform also offers a free plan for up to 30 seats.
Core capabilities: common pains and practical outcomes
- Workflows differ across teams: Configure custom workflows in ONES Project → route work through steps that match how your team operates.
- Ticket fields miss important context: Add custom fields → capture details that support your team’s planning and review.
- Sprint work is hard to track: Use sprint management → organize planned work and follow progress through the sprint.
- Routine updates take repeated effort: Set up automation → reduce manual steps for recurring work and transitions.
- Progress is difficult to see: Use built-in reporting → review project and team progress without relying on extra reporting add-ons.
- Teams depend on many plugins: Use native project management capabilities → reduce plugin reliance for supported workflows and reporting needs.
- Deployment requirements vary: Choose Cloud, On-Premise, Private Cloud, or Air-gapped deployment → align the environment with your organization’s needs.
- Project work and team knowledge are separate concerns: Pair ONES Project with ONES Wiki when useful → manage project work and knowledge within the broader ONES.com platform.
Where teams can apply it
A software team can use ONES Project to track bugs, plan sprints, automate routine transitions, and report on delivery. A team with restricted network requirements can evaluate an Air-gapped or other self-hosted deployment while retaining feature parity with Cloud.
A second scenario is an organization that wants project management without building every workflow from plugins. It can configure its processes in ONES Project, then add ONES Wiki separately if it also wants a knowledge management product. Review the deployment and workflow requirements with your team before choosing a setup.
Common Challenges When Creating Jira Issues
- The ticket is in the wrong project. This can leave work outside the right team’s queue. Check the project name and key before submitting; if it is already created, follow your team’s process for moving or recreating it.
- The issue type does not fit. Reporting and workflow steps may become confusing when a bug is filed as a story, for example. Check the project’s issue type guidance, and ask a project lead when the distinction is unclear.
- The summary is too vague. “Fix this” does not tell a teammate what to investigate. Name the affected feature and the problem or requested outcome in the summary.
- Important details are missing. A bug without reproduction steps may take longer to investigate. Add the steps, observed result, and expected result when they apply; for other work, describe what completion should look like.
- The ticket has too many unrelated tasks. Multiple outcomes can obscure ownership and progress. Separate the work into connected issues when each part can be assigned or completed independently.
Frequently Asked Questions
What information should I include when creating a Jira issue?
Include a clear summary, a useful description, the correct project, and an issue type that matches the work. Add required fields and relevant details such as priority, assignee, component, or sprint when your team uses them.
For bugs, describe how to reproduce the problem, what happened, and what you expected. For tasks or stories, explain the desired outcome and how the team can tell the work is complete.
Why can’t I create an issue in Jira?
You may not have permission to create issues in the selected project, or a required field may be missing. Check that you are in the intended project and review any message Jira displays when you submit the form.
If the form is complete and the option is still unavailable, ask a project administrator to review your permissions. Creating the ticket in a different project may send it to the wrong team and make it harder to track.
Can I change an issue type after creating a Jira issue?
In some Jira configurations, you can change an issue’s type after creation, but available options depend on project settings and permissions. Look for the issue type change option or ask a project administrator if you cannot find it.
Before changing the type, consider whether the new type fits the work and its workflow. A change can affect which fields or status steps are available, so confirm the ticket still has the details its owner needs.
How do I create a sub-task in Jira?
Open the parent issue and look for an option to add or create a sub-task. Enter a concise summary and enough detail to describe the smaller piece of work, then assign it if ownership is clear.
If you do not see a sub-task option, the project may not have sub-tasks enabled, or your account may not have the needed permission. Check the project setup with an administrator before creating a separate issue that lacks a parent link.
Conclusion
Creating a Jira issue comes down to choosing the right project and type, writing a specific summary, adding actionable details, and checking the ticket after submission. Those steps help prevent avoidable questions and make ownership clearer.
If issue creation feels confusing, focus on the work someone needs to do and the context they need to begin. A thoughtful ticket gives your team a practical path from request to action. And if your team is reviewing project management options, ONES Project offers a Jira alternative with configurable workflows, sprint management, built-in reporting, automation, and multiple deployment choices.