How to Create a New Project in Jira: Step-by-Step Guide
Need a Jira setup that works for your team? Learn how to create new project in jira, choose the right template, and get started—read now.
Creating a Jira project can take only a few minutes, but choosing the wrong project type or template can create extra setup work later. Your team may end up with confusing permissions, an unsuitable workflow, or a board that does not match how work gets done.
That’s frustrating when all you want is a clear place to plan tasks and track progress. The good news is that Jira guides you through project creation, and a few choices made upfront can save you time.
Here’s a practical walkthrough for creating a project, selecting the right setup, and preparing it for your team. I’ll also cover common setup problems and explain when a Jira alternative may be worth considering.
How to Create a New Project in Jira
To create a new Jira project, open Projects, choose Create project, select a template and project type, enter a name, then confirm the settings. You may need Jira administrator permission, depending on the project type and your site’s configuration.
- Open the project creation page. Sign in to Jira, select
Projects in the main navigation, then choose Create project. If you do not see that option, ask a Jira administrator whether your account has permission.
- Choose a project template. Pick a template that matches the work you need to manage. For example, Scrum supports work planned in sprints, while Kanban provides a continuous-flow board.
- Select the project type. Jira may offer team-managed and company-managed options. Team-managed projects let a team configure many settings independently. Company-managed projects use settings that administrators can manage more centrally.
- Enter the project details. Add a recognizable project name, such as “Mobile App Redesign.” Jira usually suggests a project key from the name. Review it carefully because the key appears in issue identifiers, such as
MAR-12.
- Review access and visibility. Check who can view and work in the project. Choose settings that fit your team’s needs, especially if the project involves confidential work or external collaborators.
- Create the project. Select
Create to finish. Jira opens the new project, where you can invite team members, create issues, and adjust project settings.
- Check the board and workflow. Create a test issue and move it through the available statuses. This quick check helps you catch mismatches before the team starts relying on the project.
But here's the truth: project creation is the easy part. A suitable template, clear permissions, and a workflow your team understands make the project useful after setup.

Choose a Project Type That Fits Your Team
Jira’s project types affect how much control the team has over configuration. A team-managed project is often a practical choice when one team wants to adjust its workflow and settings without relying on an administrator for every change.
A company-managed project can be a better fit when several teams need consistent workflows, issue types, or permission rules. For example, a software organization may want its development teams to use the same status names and reporting conventions.
Here's why: changing project types later can involve extra configuration and coordination. Before creating the project, consider who will maintain it and whether other teams need to follow the same process.
Pick a Template for the Work You Plan to Track
Templates provide a starting point for the board and workflow. A Scrum template is designed for teams that plan work in time-boxed sprints. A Kanban template suits teams that move tasks through a continuous flow.
For example, a product team preparing a two-week release cycle may choose Scrum and plan tasks into a sprint. An IT support team handling requests as they arrive may prefer Kanban, with columns for new, active, and completed work.
The best part? You can often adjust the project after creation. Still, choosing a close match at the start means less cleanup, especially when the team already has a defined way of working.
Set Up Permissions and Project Details
Project access determines who can view issues and who can make changes. Review the available roles and permission settings before inviting the full team. A small internal project may need only its core team, while a cross-functional initiative may involve several departments.
Consider the project key as well. Jira uses it in issue identifiers, so a short, memorable key helps people refer to work in messages and meetings. For a marketing campaign called “Spring Launch,” a key like SL may be easier to recognize than a longer abbreviation.
Let me explain: access and naming choices affect daily work. When teammates can identify the project and understand who can participate, they spend less time asking where tasks belong.
Configure the Board Before Your Team Starts
Open the board and confirm that its columns reflect the team’s actual workflow. A simple sequence might be To Do, In Progress, and Done. A team with formal reviews may need an additional In Review step.
Create a few sample issues and move them through the board. Check that the available issue types, statuses, and fields make sense. If a design task needs an owner and due date, confirm that teammates can add those details without a workaround.
You might be wondering: should you customize everything before launch? Start with the settings your team needs immediately. Add complexity only when real work reveals a clear gap.
Jira Alternative for Project Work: ONES.com
ONES.com brings project management and knowledge management together in one 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.

For teams comparing project systems, the practical question is how well the platform supports familiar planning and tracking tasks without requiring a collection of add-ons. ONES Project includes Jira-compatible workflows, sprint management, built-in reporting, custom workflows and fields, and automation. It also offers cloud and self-hosted deployment options.
Core Capabilities
- Teams need a familiar way to track issues. ONES Project supports Jira-compatible workflows, helping teams carry over established issue-tracking practices.
- Teams want to reduce reliance on plugins. Built-in reporting can help with common progress and project views, reducing the need to assemble separate reporting add-ons.
- A fixed workflow does not reflect how work moves. Custom workflows let teams configure work stages to match their process, making task status easier to interpret.
- Teams need project-specific information. Custom fields let teams capture details relevant to their work, so issues can hold more than a basic title and description.
- Agile teams need sprint planning. Sprint management supports planning and tracking work across iterations, giving a team a clearer view of its commitments.
- Repeated actions take time. Automation can handle routine workflow actions, helping teams reduce manual updates and keep work moving.
- Organizations need deployment choice. ONES.com offers Cloud, On-Premise, Private Cloud, and Air-gapped deployments, so organizations can select an environment that fits their requirements.
- Teams need consistent features across deployment options. The cloud and self-hosted versions have full feature parity, giving organizations more flexibility without giving up feature access.
Application Scenarios
A software team replacing or evaluating Jira can consider ONES Project when it needs sprint management, customizable workflows, reporting, and automation in a Jira alternative. The team can assess how its existing practices fit before deciding whether to move.
An organization with strict hosting requirements may evaluate On-Premise, Private Cloud, or Air-gapped deployment. This gives its administrators a way to consider project management within the organization’s chosen environment.
Common Challenges When Creating a Jira Project
- You cannot find “Create project.” Your account may not have the required permission, or the navigation may differ in your Jira configuration. Ask a Jira administrator to confirm your access and create the project if needed.
- The template does not match the team’s workflow. A Scrum board can feel cumbersome for continuous incoming work. Review how tasks arrive and progress, then choose a template that better fits the process.
- People cannot access the project. Check project roles, permissions, and visibility settings. Add the right team members and confirm their access by asking them to open the project.
- The project key is unclear. A confusing key makes issue references harder to understand. Choose a short abbreviation people can connect to the project name before creating many issues.
- The board has too many statuses. Extra steps can make progress harder to read. Start with the stages the team genuinely uses, then add a status when a recurring need becomes clear.
Frequently Asked Questions
What permission do I need to create a Jira project?
The required permission depends on your Jira setup and the project type. Company-managed project creation commonly requires Jira administrator access, while team-managed creation may be available to people with the appropriate project-creation permission. If the creation option is missing, ask your Jira administrator to check your access. An administrator can also create the project and assign you the role you need to manage it.
Should I create a team-managed or company-managed project?
Choose team-managed when one team needs greater control over its project configuration. Choose company-managed when administrators need to maintain shared settings across multiple projects or teams. For example, a small product group may prefer independent configuration, while a larger organization may need consistent workflows and permissions. Consider who will maintain the setup before you choose.
Can I change a Jira project after creating it?
Yes, many project settings can be adjusted after creation, including workflows, fields, and access settings, depending on the project type and your permissions. However, major changes can take planning, particularly when many issues or teams are involved. Start with a sensible template and a simple workflow, then make changes when you understand what the team actually needs.
What should I do if my team uses a different workflow from the template?
First, identify the stages the team uses to move work from request to completion. Then compare those stages with the project’s workflow and board columns. Adjust the available settings if your project type and permissions allow it. For instance, a design team may add a review stage, while a service team may use a waiting status for requests that need more information.
Can I create a Jira project without administrator access?
Sometimes. Jira administrators can control whether other people are allowed to create projects, and permissions may differ by project type. If you can open Jira but cannot find the creation option, contact your administrator rather than trying to work around access controls. You can explain the project’s purpose, the people who need access, and the template you want to use.
Conclusion
To create a Jira project, select Projects and Create project, choose a suitable template and project type, then set a clear name and review access. Test the board before inviting everyone to use it.
A rushed setup can lead to confusing workflows and permission problems, but a few thoughtful choices make the project easier to use. Start with the team’s real process, keep the configuration focused, and adjust it as work evolves. If you are comparing platforms, ONES Project is a Jira alternative with familiar workflows and cloud or self-hosted deployment options.