How to Create a New Project in Jira: Full Step-by-Step Guide
Wondering how to create a new project in Jira? Follow this step-by-step guide to choose the right template, project type, and access settings. Read now!
Creating a Jira project takes only a few minutes when you know which project type and template fit your team. In Jira Cloud, start from Projects, select Create project, choose a template, set the project type, and give the project a name. Then check access and create it.
But here's the truth: a rushed setup can leave you with the wrong permissions, confusing workflows, or a project that does not match how your team works. Changing those choices later may take extra admin time and interrupt active work. You might also see different options depending on your Jira version and permissions.
Here's why a few careful decisions matter: they give your team a clear place to plan, track, and report work. I’ll walk you through each choice, explain what to configure after creation, and show you how to avoid common setup snags.
How to Create a New Project in Jira
Follow these steps in Jira Cloud. Labels and menus can vary slightly by Jira version, but the setup decisions remain similar.
Check your access. Sign in to Jira and confirm you have permission to create projects. If the creation option is missing, ask a Jira administrator to grant access or create the project for you.
Open project creation. Select Projects in the navigation, then choose Create project. In some layouts, you may find project creation under a More menu.
Choose a project template. Pick a template that matches the work you need to manage. Scrum and Kanban templates suit software teams; a task-tracking template may fit a general team. Review the template description before continuing.
Select the project type. Jira commonly offers team-managed and company-managed projects. Team-managed projects let a team control many settings independently. Company-managed projects give administrators more centralized control over shared schemes and configuration.
Enter the project details. Add a clear project name, such as “Mobile App Launch.” Jira may suggest a project key, a short identifier used in issue keys. Review the suggested key and change it if your Jira setup allows.
Review access settings. Choose who can view and work in the project. For a confidential launch, restrict access to the relevant team. For cross-functional work, make sure the intended collaborators can participate.
Create the project. Check the template, project type, name, key, and access settings. Select Create when everything looks right. Jira opens the new project, where you can begin organizing work.
Set up the first work items. Create a few representative tasks, assign owners, and add due dates where useful. Check that each issue type and status reflects how your team will track progress.
The fastest setup is not always the best setup. Taking a moment to choose the right project type and access level can prevent a cleanup later.

Choose a Project Type and Template That Fit
A template gives you a starting structure for the work. For example, a software team running time-boxed sprints may choose Scrum, while a support team handling incoming requests may prefer Kanban.
Team-managed projects are useful when a team needs room to adjust its own settings. A small product group can shape its workflow without relying on an administrator for every change.
Company-managed projects make sense when several teams need shared settings and consistent reporting. For example, an organization coordinating multiple engineering teams may want common issue types and workflows.
Let me explain: the choice affects how much control sits with the team and how much stays centralized. If you are unsure, ask your Jira administrator how your organization manages workflows and permissions before choosing.
Configure the Project After Creation
Once Jira creates the project, confirm that its basic setup supports real work. Create a sample issue and move it through the statuses your team expects to use.
Imagine a design request moving from “To do” to “In progress,” then to “Review” and “Done.” If the project lacks a review status, team members may track that stage inconsistently.
Check roles and permissions with a teammate who should have access. Ask them to open the project and perform a routine action, such as creating or updating an issue.
The best part? A short test can reveal problems before the project fills with active work. Review notifications, issue types, and board settings while the project is still easy to adjust.
Common Setup Choices That Cause Trouble
A vague project name can make search results confusing. “Team Work” tells people little; “Customer Portal Redesign” gives collaborators a clearer signal.
Choosing a template only because it appears first can also create friction. A team handling continuous requests may struggle with a sprint-focused board if work does not arrive in planned batches.
Access settings deserve an early check. If an intended collaborator cannot view issues, work may move into private messages and become difficult to follow. If sensitive work is visible too broadly, an administrator may need to tighten permissions.
Finally, avoid adding complicated statuses before you understand the team’s process. Start with a practical workflow, test it with real tasks, and add complexity only when it solves a specific problem.
Keep Project Setup Manageable as Work Grows
As a project grows, agree on a few conventions for issue names, priorities, and ownership. For example, a product team might ask everyone to begin task summaries with a clear action, such as “Review onboarding emails.”
Use a regular check-in to spot setup issues. If work repeatedly stalls in one status, ask whether the workflow needs adjustment or ownership is unclear.
Reporting becomes more useful when teams enter information consistently. If one group marks work “Blocked” while another uses comments for the same situation, project reports may miss important patterns.
Start with the smallest setup that supports the work in front of you. Then make changes when an actual team need emerges, instead of trying to predict every future scenario on day one.

Value Proposition
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 provides knowledge management as a Confluence alternative. They are sold separately, so you can choose the product that fits your team.
Core Capabilities
Problem: Rebuilding familiar Jira workflows can slow a team’s move to another platform. ONES capability: ONES Project supports Jira-compatible workflows. Result: Your team can carry familiar work patterns into a different project management environment.
Problem: Repeated reporting work can take time away from planning. ONES capability: Built-in reporting helps teams review project progress. Result: You can see useful project information without assembling every report manually.
Problem: A standard workflow may not reflect your approval or delivery process. ONES capability: Custom workflows let teams shape work stages. Result: Tasks can follow a process that better reflects how the team operates.
Problem: Teams may need to capture details that standard fields do not cover. ONES capability: Custom fields support additional project information. Result: The team can track relevant details in its work items.
Problem: Sprint planning can feel disconnected from everyday issue tracking. ONES capability: ONES Project includes sprint management. Result: Teams can organize planned development work alongside their project tasks.
Problem: Repetitive steps can create avoidable manual work. ONES capability: Automation supports rule-driven actions. Result: Teams can reduce routine follow-up when a suitable automation is configured.
Problem: A long list of add-ons can make an environment harder to maintain. ONES capability: Native project features cover workflows, reporting, fields, sprints, and automation. Result: Teams may reduce reliance on plugins for those needs.
Problem: Some organizations need to keep project management within their own infrastructure. ONES capability: ONES.com offers Cloud, On-Premise, Private Cloud, and Air-gapped deployments, with feature parity between cloud and self-hosted versions. Result: You can assess deployment options alongside team requirements.
Application Scenarios
A software team reviewing Jira alternatives: A team that already relies on sprint planning and customized workflows can evaluate ONES Project against those needs. It can check workflow compatibility, reporting, and automation before planning a transition.
An organization with infrastructure requirements: A company that needs an on-premise or air-gapped deployment can assess the deployment options while checking whether the project features match its delivery process.
A team connecting project work with internal knowledge: A group that wants project management and knowledge management within one platform can consider ONES Project and ONES Wiki. Since they are sold separately, the team can select only the product it needs.
Common Challenges When Creating a Jira Project
You cannot see the creation option. Your Jira account may lack project creation permission. Ask an administrator to confirm your access or create the project with the settings you provide.
You are unsure which template to choose. Describe how work arrives and moves through your team. A continuous stream of requests often suits Kanban; planned sprints may call for Scrum.
Your project key is unavailable or confusing. Jira may suggest a key that is already in use or does not match team conventions. Try a short, recognizable variation and check it before creation.
Teammates cannot access the project. Review project roles and permissions with an administrator. Test access with a teammate who should be able to view and update issues.
The project feels too complicated after setup. Remove unnecessary statuses or fields where your permissions allow. Keep the workflow focused on decisions the team makes regularly.
Frequently Asked Questions
Can I create a Jira project without being an administrator?
That depends on the permissions configured for your Jira environment. Some organizations allow project creation for a wider group, while others reserve it for Jira administrators. If you do not see the creation option, ask your administrator to check your permissions. You can also share the project name, template, access needs, and team-managed or company-managed preference so the administrator can set it up correctly.
What is the difference between team-managed and company-managed projects?
Team-managed projects give a team more direct control over many project settings. Company-managed projects use more centralized administration, which can help organizations maintain shared configurations across teams. The right choice depends on how much autonomy your team needs and whether your organization relies on standard workflows. Ask your Jira administrator about local conventions before choosing, especially if multiple teams need consistent reporting.
Can I change the project template after creating a Jira project?
Some settings can be changed after creation, but switching to a different template may not be a simple one-click change. The available options depend on the project type and Jira configuration. Before creating the project, compare the template’s board and workflow with your team’s actual process. If the project already exists, check the relevant settings or ask an administrator before making structural changes.
What should I name my Jira project?
Choose a name that tells teammates what the work is about, such as “Mobile App Launch” or “Customer Support Improvements.” Avoid names that could describe many unrelated efforts. Jira may also assign a short project key that appears in issue identifiers. Review that key for clarity and check whether your organization has naming conventions before you finish creating the project.
Can a Jira project be private?
Access depends on the project’s permissions and the configuration available in your Jira environment. During setup, review who can view and work in the project. For confidential work, confirm the settings with an administrator and test access with an appropriate teammate. Do not assume a project is restricted simply because its name sounds private; verify the actual permissions after creation.
Conclusion
To create a Jira project, open project creation, select a template, choose a project type, enter the project details, review access, and create a few test issues. Those choices shape how clearly your team can organize work and how easily collaborators can participate.
A rushed setup can create confusion around workflows and permissions, but a short review helps you catch problems early. Start with the process your team uses today, test the project, and adjust it as real needs appear. If you are comparing approaches, ONES.com is another option to evaluate for project and knowledge management.