How to Create a New Jira Project: A Step-by-Step Tutorial
Need help with jira create new project setup? Choose the right template and project type with this step-by-step guide. Click to get started.
Creating a Jira project can feel like a quick setup task, until you’re staring at unfamiliar templates, project types, and permission options. Pick the wrong setup and your team may end up with cluttered boards, unclear ownership, or workflows that don’t match how work actually moves.
That uncertainty can slow down a project before anyone adds the first task. You may also wonder whether a project is the same thing as a board, or whether you need an administrator to get started.
Here’s the practical route: choose a template that fits your work, select the right project type, set a clear name and key, then check access and workflows. I’ll walk you through each step, explain what to configure next, and help you avoid common setup mistakes.
How to create a new Jira project
In Jira Cloud, open Projects, choose Create project, select a template and project type, enter the project details, then create it. Your available choices may depend on your Jira plan and permissions.
- Open project creation. From the top navigation, select
Projects and then Create project. If you don’t see that option, check with your Jira administrator about your permissions.
- Choose a template. Pick a workflow that matches the team’s work. Scrum is designed for work planned in sprints; Kanban is useful when work moves continuously through stages.
- Select a project type. Jira may offer a team-managed or company-managed project. Team-managed projects let a team handle many settings independently. Company-managed projects use configurations managed more centrally.
- Enter the project details. Add a clear name, such as “Website Relaunch,” and review the project key Jira suggests. A short key like
WEB makes issue identifiers easier to recognize.
- Review access and settings. Choose the access option that fits your team and organization. Check the project type, template, and any available permissions before continuing.
- Create the project. Select
Create to finish setup. Jira opens the new project, where you can add issues, invite teammates, and adjust the board or workflow.
That creates the project space, but it doesn’t automatically organize every detail of the team’s work. Take a few minutes to confirm the board, permissions, and workflow before inviting everyone.

Choose the right Jira project type
The project type affects who manages settings and how consistently those settings are applied. In a small team, independent configuration can be convenient. In a larger organization, central oversight may help keep processes consistent.
When a team-managed project fits
Choose team-managed when the team needs to adjust its own workflows and board settings without relying on a Jira administrator for every change. For example, a five-person design team may want to add a review status as its process develops.
This flexibility can make setup feel approachable. Still, agree on basic conventions first, especially if other teams need to report on similar work.
When a company-managed project fits
Company-managed projects suit teams that need shared workflows, fields, or permission schemes maintained centrally. A product organization with several delivery teams might use this structure to keep issue statuses and reporting consistent.
These projects can involve more administrator coordination. Before choosing this option, ask who will maintain the configuration and how changes should be requested.
Pick a template that matches the work
A template gives your project a starting structure. The best choice reflects how work arrives and moves, rather than what sounds most familiar.
| Work pattern | Possible starting point | Example |
| Work is planned and completed in time-boxed cycles | Scrum | A software team plans a two-week sprint and reviews completed work. |
| Work arrives continuously and moves through stages | Kanban | A support team tracks requests from “To do” through “In progress” to “Done.” |
| Work needs a tailored process | A suitable business or software template | A marketing team tracks campaign planning, review, and launch. |
Here’s why the choice matters: templates can shape the board and issue types you see immediately. A team that works from a continuous queue may find sprint planning adds unnecessary steps.
You can often adjust settings later, but a close fit at the start saves cleanup. If two templates seem plausible, ask the team to describe a typical task from request to completion.
Set a useful project name, key, and access level
Use a name that tells people what the project is for. “Mobile App Release” is clearer than “Team Project,” especially when people have access to several Jira spaces.
Jira also uses a project key in issue identifiers, such as APP-42. Keep it short and recognizable. If your organization already uses naming conventions, follow them so issues are easy to identify across teams.
Access settings deserve equal attention. A public project may expose work to a wider group than intended, while restrictive access can prevent teammates from viewing or updating issues.
For example, an internal product launch may need access for product, design, and engineering. A confidential hiring initiative may need a smaller, carefully selected group.
What to configure after creating the project
Before the team begins adding work, check that the new project supports its everyday workflow. A quick review now can prevent repeated questions later.
- Board columns: Match the visible stages to the team’s real process. If work routinely waits for review, include a review stage rather than hiding that status.
- Issue types: Confirm that the project has the work categories the team needs, such as tasks, bugs, or stories.
- Permissions: Check who can browse, create, edit, and administer project work.
- Notifications: Review which changes notify people. Too many alerts can make important updates easy to miss.
- Reports: Check that the available reports answer useful questions, such as what remains in a sprint or where work is waiting.
Try one realistic task before inviting the full team. Create an issue, move it across the board, assign it, and confirm that the expected people can see it.
Value proposition: If your team wants project management with configurable workflows and built-in reporting, ONES Project is a Jira alternative within ONES.com. ONES Project and ONES Wiki are sold separately.

ONES.com is a unified platform for project management and knowledge management, powered by ONES Assistant. For teams focused on project delivery, ONES Project provides project management capabilities without requiring you to assemble every part of the workflow through add-ons.
Core capabilities
- Plugin sprawl: ONES Project includes features such as sprint management and reporting, helping teams handle common project needs with fewer separate plugins.
- Workflows that don’t fit: Custom workflows let teams reflect their actual review and delivery stages, so work can move through a process that makes sense to them.
- Fields that miss key details: Custom fields capture information relevant to a team’s work, making issues more useful during planning and review.
- Sprint planning needs: Sprint management supports teams that plan work in cycles, helping them organize tasks around a defined period.
- Repeated manual actions: Automation can handle recurring workflow actions, reducing routine steps and helping teams apply rules consistently.
- Existing Jira habits: Jira-compatible workflows can make it easier for teams familiar with Jira-style processes to adapt their project setup.
- Deployment constraints: ONES.com offers Cloud, On-Premise, Private Cloud, and Air-gapped deployments, giving organizations different hosting options.
- Concern about feature differences: Cloud and self-hosted versions have full feature parity, so deployment choice doesn’t mean choosing a reduced feature set.
Application scenarios
A software team can use ONES Project to plan sprints, customize issue fields, automate recurring steps, and review project progress through built-in reporting. This can be useful when a team wants a Jira alternative and aims to reduce reliance on separate plugins.
An organization with strict hosting requirements can consider On-Premise, Private Cloud, or Air-gapped deployment options. Teams can also try the free plan for up to 30 seats before deciding whether the platform fits their needs.
ONES Project is a distinct product from Jira, so review its workflows and deployment options against your team’s requirements before migrating. If the organization also wants a knowledge management tool, ONES Wiki is available separately as a Confluence alternative.
Common challenges when setting up a Jira project
The create option isn’t available
Problem: You can open Jira but don’t see the option to create a project. Solution: Ask your Jira administrator to check your permissions or create the project for you. Share the intended project name, template, type, and access needs to make the request actionable.
The board doesn’t match the team’s process
Problem: The default board has stages that don’t reflect how work moves. Solution: Map the team’s actual steps before changing columns or statuses. For example, if tasks need approval before completion, decide where that review belongs in the workflow.
People can’t see or update issues
Problem: Teammates report access errors after the project is created. Solution: Review project permissions and confirm that the right people or groups have the required access. Test with a teammate who represents the intended audience.
The project key is confusing
Problem: Issue identifiers are hard to recognize among other work. Solution: Use a short, distinctive key that follows your organization’s conventions. Check whether Jira allows the key to be changed in your setup before creating many issues.
Frequently asked questions
Can I create a Jira project without being an administrator?
It depends on your organization’s Jira permissions. Some accounts allow project creation for a wider group, while others reserve it for administrators. If you can’t find Create project, ask your Jira administrator whether your account can receive permission or whether they can create the project for you.
What’s the difference between a Jira project and a board?
A project organizes issues, settings, and permissions around a body of work. A board presents work in a visual format, such as columns for status or a sprint view. Teams may use a board to manage issues from one or more projects, depending on its configuration.
Can I change the template after creating a project?
Some parts of a project, such as workflows and board settings, can be adjusted after creation. Changing the underlying project setup may be more involved, and available options vary by project type and Jira configuration. Choose the closest template first, then check which settings your team can safely modify.
Should I choose a team-managed or company-managed project?
Choose based on how your team needs to manage settings. Team-managed projects give teams more independence for many configuration choices. Company-managed projects are useful when administrators need to maintain shared workflows or permissions across teams. If you’re unsure, ask who will own ongoing configuration before creating the project.
Conclusion
To create a Jira project, open project creation, choose a suitable template and project type, enter a clear name and key, then review access before confirming. Afterward, test a realistic task and check the board, permissions, and notifications.
But here's the truth: a project that’s easy to create can still become frustrating if its workflow doesn’t fit the team. A short setup review helps prevent confusion and gives everyone a clearer place to manage work.
If your requirements point beyond Jira, compare alternatives such as ONES Project against your workflow, deployment, and reporting needs. Choose the setup that makes everyday work easier to understand and manage.