How to Create a New Project in Jira: 7 Simple Steps (2026)
Wondering how do i create a new project in jira? Follow 7 simple steps to choose the right template, settings, and access. Read now to get started.
A new Jira project can feel straightforward until you reach the template, project type, and access settings. Choose the wrong setup, and your team may inherit confusing boards, excess permissions, or settings that are awkward to change. That friction can slow the first sprint before anyone adds a task.
How do you create a new project in Jira? Open Projects, select Create project, choose a template, configure the project type and details, then create it and check access. I’ll walk you through seven steps, including what to decide before clicking and what to verify afterward. But here’s the truth: a project is more than a name and a board. A few thoughtful choices now can give your team a usable workspace from day one.
Create a Jira project in 7 steps
These steps focus on Jira Cloud. Your menus may look slightly different depending on your Jira product, account permissions, and current interface.
-

Step 1: Check that you have permission to create projects
Sign in to Jira and check whether the Create project option is available. Project creation is generally controlled by Jira administrator permissions, so you may need an administrator to create it for you.
If the option is missing, ask your Jira administrator whether your account can create projects. Share the project’s purpose, team, and preferred template so they can set it up correctly.
-
Step 2: Open the project creation screen
In the Jira navigation, open Projects and select Create project. In some Jira layouts, you may see a View all projects option before you can start creating one.
If your organization uses several Jira products, check that you’re creating the project in the right one. A software team, service desk, and business team may need different project features.
-
Step 3: Choose a project template
Jira templates provide a starting point for the way your team tracks work. A Scrum template suits teams that plan work in sprints. A Kanban template suits teams that move tasks through a continuous workflow.
Other templates may focus on business work, service requests, or specific team needs. For example, a product team planning two-week sprints could start with Scrum, while an operations team handling incoming requests might prefer Kanban.
Here’s why: a template can shape the board, issue types, and workflow your team sees first. Choose the closest match to your actual process, rather than selecting a template only because its name sounds familiar.
-
Step 4: Select the project type
Jira may ask whether you want a team-managed or company-managed project. Team-managed projects let teams control more settings independently. Company-managed projects allow administrators to manage configurations across projects.
Choose team-managed when a small team needs room to adjust its own setup. Consider company-managed when your organization needs shared workflows or centralized administration. If you’re unsure, check your team’s Jira standards before continuing.
-
Step 5: Enter the project name and key
Give the project a clear name that team members will recognize, such as Website Redesign or Customer Support Operations. Jira may generate a project key from the name; you can often edit it during setup.
Keep the key short and easy to identify. It appears in issue identifiers, such as WEB-12, so a clear key helps people recognize a task’s project when they see it in a notification or board.
-
Step 6: Set access and finish creating the project
Review the access or visibility options shown during setup. The available choices depend on your Jira configuration and permissions. Decide who should be able to view the project and who should be able to work in it.
When the details look right, select Create project. Jira creates the project and takes you to its main workspace, where you can begin adding issues or adjusting project settings.
-
Step 7: Check the project and invite the right people
After creation, check the project name, key, template, board, and access settings. Add the teammates who need to plan or complete work, and confirm that they can see the project and its tasks.
Create a sample issue and move it through the workflow to test the setup. For example, add a task, assign it to a teammate, and move it from To Do to In Progress. This quick check can reveal missing permissions or an unsuitable workflow before real work begins.
Choose the right project setup before you start
A project name tells people what the work concerns, but the template and project type affect how they manage it. Think about the team’s work pattern before you choose: do people pull tasks continuously, or plan a fixed amount of work for each sprint?
For example, a marketing team handling a steady stream of campaign requests may benefit from a Kanban-style board. A software team agreeing on sprint goals may find a Scrum template more useful. You can make a better choice by considering what the team already does.
You might be wondering: should you choose team-managed or company-managed? Start with the amount of control your team needs and the consistency your organization expects. If several teams must use the same workflow, ask an administrator about company-managed settings before creating separate project configurations.
What to configure after Jira creates the project
Creating the project gives you a place to track work, but the initial setup may not match every team’s process. Review the board columns, issue types, and workflow statuses. A three-person design team may need only a few statuses, while a release team may need additional review and testing stages.
Next, add a small set of representative tasks. Include a typical task, a larger piece of work, and anything that requires review. This makes it easier to see whether the board and issue details help people understand what needs attention.
The best part? A short trial run often shows what needs attention before the board fills up. Ask two or three teammates to create and update tasks, then adjust settings that cause confusion. A clear workflow can help prevent stalled work and repeated status questions.
Manage project access and permissions carefully
Access settings determine who can view and work in a project. The exact controls depend on your Jira plan and configuration, but it’s worth checking them as part of the initial setup rather than waiting until someone cannot see a task.
Give people access according to their responsibilities. For instance, a project team may need to create and update issues, while an occasional stakeholder may only need to view progress. Ask your Jira administrator about the available roles and permission settings.
Let me explain: broad access can expose work to people who do not need it, while overly narrow access can block legitimate collaboration. Test access with a teammate who should participate and, where appropriate, check how the project appears to someone outside the project team.
Fix common problems when creating a Jira project
If Create project is missing, check your permissions first. A Jira administrator can confirm whether your account can create projects or set one up on your behalf. Include the project name, intended team, and preferred template in your request.
If you cannot find a suitable template, compare the available options against your team’s everyday workflow. A basic Scrum or Kanban template may be a better starting point than a specialized template that adds stages your team will not use.
If the project exists but teammates cannot access it, review its permissions and invite the right people. When a board looks confusing, test the workflow with a few sample tasks and simplify statuses or columns that do not reflect real work.
ONES.com brings project management and knowledge management together on one platform. For teams evaluating a Jira alternative, ONES Project provides project management capabilities, while ONES Wiki provides knowledge management; the products are sold separately.

Here’s why it may be relevant: teams that manage work across many plugins or need self-hosted deployment can compare ONES.com’s capabilities and deployment choices with their current Jira setup. ONES.com offers Cloud, On-Premise, Private Cloud, and Air-gapped deployments, with feature parity between its cloud and self-hosted versions.
Core capabilities
- Need Jira-compatible workflows? ONES Project supports Jira-compatible workflows, helping teams retain familiar ways to move work through stages.
- Relying on multiple plugins? Built-in reporting and automation can reduce the need to add plugins for common tracking and reporting needs.
- Struggling with a rigid process? Custom workflows and fields let teams shape how issues are tracked, making project details more relevant to their work.
- Planning work in sprints? Sprint management helps teams organize planned work and track progress during a development cycle.
- Keeping project guidance separate from delivery? ONES Wiki provides knowledge management alongside ONES Project, so teams can choose the separate product that suits their needs.
- Need to manage project data on your own infrastructure? On-Premise and Private Cloud options give organizations self-hosted deployment choices.
- Working in a restricted network? An Air-gapped deployment supports teams that need an environment without external network connectivity.
- Want to start with a smaller team? The free plan supports up to 30 seats, giving eligible teams a way to try the platform before expanding.
Where teams might apply it
A software team moving away from scattered project plugins could evaluate ONES Project’s workflows, sprint management, reporting, and automation together. The team can compare those capabilities with the Jira setup it relies on today, then decide whether a change fits its working practices.
An organization with strict network requirements could assess the On-Premise, Private Cloud, or Air-gapped deployment options. A team that also wants a separate knowledge management product could consider ONES Wiki alongside ONES Project, keeping in mind that the products are sold separately.
Common challenges when setting up a new project
- The template does not fit the work. Teams may spend time updating statuses that do not reflect how tasks move. Choose the closest workflow during setup, then test it with representative tasks and refine it with the team.
- The project key is hard to recognize. Unclear issue identifiers can make messages and task references difficult to follow. Agree on a short, recognizable key before creation, especially when several projects have similar names.
- People cannot access the project. Teammates may be invited without having the right permissions. Check access after creation and ask an administrator to review roles if expected team members cannot view or update issues.
- The board becomes cluttered quickly. Too many statuses or columns can make work harder to scan. Start with the stages the team actually uses, then add detail only when it helps people make decisions.
Frequently asked questions
Can I create a Jira project without being an administrator?
It depends on your Jira permissions. Project creation is generally controlled by administrator settings, so you may not see the creation option on your account. If you cannot create a project, ask your Jira administrator to check your permissions or create the project for you. Provide the project purpose, team, and preferred template to help them configure it appropriately.
What is the difference between team-managed and company-managed Jira projects?
Team-managed projects give a team more direct control over its project settings. Company-managed projects allow administrators to manage configurations centrally and support consistency across projects. The best fit depends on how much independence your team needs and whether your organization expects shared workflows. If you are unsure, check with your Jira administrator before creating the project.
Can I change a Jira project template after creating the project?
Some project settings can be adjusted after creation, but changing to a different template may not be a simple one-click switch. Templates can configure workflows, issue types, and boards in different ways. Before creating the project, choose the closest match to your team’s work. If you already created it, ask your Jira administrator to review the available changes before making large configuration edits.
What should I do if teammates cannot see my new project?
Check the project’s access settings and confirm that the right people have been added with suitable permissions. The exact controls vary with your Jira setup, so an administrator may need to review project roles or broader permissions. Test access with a teammate who should participate. If that person still cannot see or update work, share the project name and the issue they encounter with your administrator.
Conclusion
Creating a Jira project means choosing a template, project type, name, key, and access settings that fit the team’s work. After Jira creates it, test the board with sample tasks and confirm that teammates can participate.
But here’s the truth: a project that looks ready may still need a small adjustment once people use it. A quick test can catch confusing workflows and access gaps before they disrupt a sprint. With a thoughtful setup, your team can start tracking work in a workspace that makes sense from day one.