How to Create a New Jira Project: Step-by-Step Guide (2026)
Not sure how to create new project in Jira? Follow this 2026 guide to choose the right setup and avoid workflow issues—read now.
Creating a Jira project is straightforward once you know which project type and template fit your team. Choose poorly, though, and you may end up with confusing workflows, missing permissions, or a board that doesn’t match how work gets done. Fixing those choices later can disrupt active tasks and make reporting harder to trust.
But here's the truth: a few careful decisions before you click Create can prevent most setup headaches. I’ll walk you through the Jira project creation steps, explain the choices that matter, and show you how to check your setup before inviting everyone in. You’ll also see what to do if you can’t create a project or need a setup that supports more control.
How to Create a New Project in Jira
To create a Jira project, open the project creation option, choose a project type and template, set a name and key, then review access and settings. The exact labels may vary by Jira edition, permissions, and interface updates.
-
Check that you have permission. In Jira Cloud, project creation is generally controlled by a Jira administrator or a permission assigned to your account. If you don’t see a create-project option, ask your Jira admin to confirm your access.
-
Open the project creation flow. In the navigation, look for Projects and select Create project. In some Jira layouts, you may find the same action through the project directory or an administration menu.
-
Choose a project template. Select a template that fits the work, such as Scrum for sprint-based software delivery, Kanban for continuous work, or a business template for tasks such as service requests. Templates determine which features and starting workflow are available.
-
Select a project management style. If Jira offers team-managed and company-managed options, consider who should control settings. Team-managed projects let a team configure many details independently. Company-managed projects use shared schemes and centralized administration.
-
Enter the project name and key. Use a name people can recognize, such as “Website Redesign.” Jira may suggest a short key, such as “WEB.” The key appears in issue identifiers, so choose something clear and easy to distinguish from existing projects.
-
Review access and create the project. Check whether the project is open to the organization or restricted to specific people. Confirm the details, then select Create. Jira may take you directly to the new project or its board.
-
Check the setup before adding work. Open a test issue, confirm the board columns and issue types, and check who can view or edit project work. If the project uses a shared configuration, ask an administrator before changing settings that could affect other teams.
Here’s why: Jira projects can share workflows, permission schemes, and other settings, depending on how they’re managed. A quick review now helps you avoid changing an option that affects more than one team.

Choose the Right Jira Project Type and Template
The template should reflect how your team moves work, rather than simply matching its department name. A software team that plans regular sprints may need Scrum; a support team handling requests as they arrive may work better with Kanban.
For example, imagine a marketing team managing campaign approvals. A business project template may offer a simpler task flow than a software development template with sprint planning and development-specific issue types. The best starting point is the one that resembles your real process.
Jira’s management style matters, too. Team-managed projects suit teams that need room to adjust their own setup. Company-managed projects can help administrators maintain consistency across several projects, but changes may require more coordination.
Quick template comparison
| Team need | Possible starting point | What to consider |
| Work planned in time-boxed sprints | Scrum | Confirm that the team will plan and review work in sprint cycles. |
| Ongoing work with changing priorities | Kanban | Set clear board columns and decide how the team will manage work in progress. |
| Requests, campaigns, or operational tasks | Business template | Check that its issue types and workflow match the team’s approval process. |
Set a Clear Project Name, Key, and Access Model
A project name should make sense to someone who wasn’t in the setup meeting. “Customer Portal Refresh” tells teammates more than “Phase 2,” especially when several projects appear in the same Jira workspace.
The project key is shorter, but it matters every time someone references an issue. For instance, “CPR-18” is easier to recognize when CPR is reserved for the customer portal project. Before accepting Jira’s suggested key, check that it won’t be confused with an existing team or initiative.
Then decide who needs access. A broad audience can help when many teams collaborate, while a restricted project may be more suitable for confidential planning. Let me explain: access settings influence whether people can find project work and what actions they can take.
Configure the Board and Workflow Before Launch
After creating the project, review the board columns and status flow. A team that uses “To do,” “In progress,” and “Done” may not need a complex workflow. A release team with testing and approval stages may need more specific steps.
Try a sample issue from start to finish. If a task moves from “To do” to “In progress” and then “Done,” check that each transition is available to the right people. This small test often reveals mismatched statuses or missing permissions before the team depends on the board.
Also review issue types and required fields. A team tracking bugs, stories, and technical tasks may need all three, while a small operations group may need only tasks and requests. The best setup keeps useful detail without making every new issue slower to create.
Invite Teammates and Test the Project
Invite only the people who need to participate at launch, then confirm they can perform their expected tasks. A contributor should be able to create or update issues; a viewer may only need visibility into progress.
You might be wondering: should you add every possible field and status before launch? Usually, it’s easier to begin with the essentials, then adjust after the team has completed real work. For example, if several tasks stall while waiting for review, add a review status rather than guessing in advance.
Before announcing the project, check the board, issue creation, notifications, and access from a teammate’s perspective. If the project connects with other Jira projects or tools, test the relevant workflow as well. A short launch check can catch confusing settings while changes are still easy to manage.
Project Management Alternative: ONES.com
Value proposition: ONES.com combines project management and knowledge management in one platform, with ONES Project for project work and ONES Wiki for knowledge management. The products are sold separately, so you can choose the capability that fits your needs.

If your team is creating a Jira project because it needs structured work tracking, ONES Project is a Jira alternative. It supports Jira-compatible workflows alongside project settings and reporting, with deployment options that include cloud and self-hosted environments.
Core capabilities
- Pain: Teams need familiar issue workflows when evaluating a change. ONES capability: ONES Project supports Jira-compatible workflows. Result: Teams can carry familiar process patterns into a different project management environment.
- Pain: Standard fields don’t capture the details a team needs. ONES capability: Teams can configure custom fields and workflows. Result: Work items can reflect the team’s process without relying on a one-size-fits-all setup.
- Pain: Sprint planning is difficult to coordinate across active work. ONES capability: ONES Project includes sprint management. Result: Teams can plan and track work in sprint-based cycles.
- Pain: Manual updates take time and may be missed. ONES capability: Automation supports repeatable project actions. Result: Teams can reduce routine handling for common workflow events.
- Pain: Project leads need visibility into progress. ONES capability: Built-in reporting provides project insights. Result: Teams can review progress without relying entirely on manually assembled updates.
- Pain: A team wants to avoid adding a plugin for every missing feature. ONES capability: ONES Project includes core project management capabilities within the platform. Result: Teams may be able to reduce plugin dependence for supported needs.
- Pain: An organization needs control over where its project environment runs. ONES capability: ONES.com offers Cloud, On-Premise, Private Cloud, and Air-gapped deployments. Result: Teams can choose an environment that suits their infrastructure requirements.
- Pain: Self-hosted teams worry about losing functionality. ONES capability: The cloud and self-hosted versions have full feature parity. Result: Deployment choice does not mean choosing a reduced feature set.
ONES.com offers a free plan for up to 30 seats. Its AI-powered platform includes ONES Assistant, though AI pricing is a separate consideration and isn’t needed to evaluate ordinary project setup.
Application scenarios
A software team replacing Jira: A team can assess ONES Project’s Jira-compatible workflows, sprint management, and reporting against its existing delivery process. That comparison helps reveal which workflows need to carry over and which can be simplified.
An organization with restricted infrastructure: A company with strict hosting requirements can consider On-Premise, Private Cloud, or Air-gapped deployment. The availability of those options can matter when cloud hosting doesn’t fit internal requirements.
A team connecting project work with knowledge management: An organization can use ONES Project for project management and choose ONES Wiki separately for knowledge management. That arrangement may suit teams that want related capabilities without treating them as a single required purchase.
Common Challenges When Creating a Jira Project
- You can’t find the create-project option. Your account may not have project creation permission. Ask a Jira administrator to confirm the required access rather than changing unrelated settings.
- The project key is already in use or confusing. Choose a distinct abbreviation that teammates can recognize in issue references. Check existing project keys before settling on one.
- The template feels too complex. Start with the closest suitable template, then remove unnecessary steps or fields where your permissions allow. Ask an administrator before changing shared configurations.
- Teammates can’t see or edit work. Review project access and role assignments with an administrator. Confirm the difference between viewing a project and being allowed to create or transition issues.
- The board doesn’t match the team’s process. Compare its columns and statuses with the actual route a task takes. Update the workflow carefully, especially when other projects may share its configuration.
FAQs
Can I create a Jira project without being an administrator?
Possibly. Project creation depends on permissions set by your Jira administrator, and those permissions can differ across organizations. If you don’t see a create-project option, ask your Jira admin whether your account can create projects or whether they need to create one for you. Avoid changing administration settings without approval, especially if your team uses shared project configurations.
What is the difference between team-managed and company-managed Jira projects?
Team-managed projects give a team more independence over many project settings. Company-managed projects use centrally administered schemes and configurations, which can help maintain consistency across multiple projects. The right choice depends on how much local flexibility your team needs and whether administrators need to standardize workflows, fields, or permissions.
Can I change the project key after creating a Jira project?
Jira may allow project details to be edited, but the available options depend on your permissions and Jira setup. Changing a project key can affect issue references, integrations, links, and team habits. Before changing it, check the impact with your Jira administrator and confirm that connected tools won’t rely on the existing key.
Can I create a Jira project from an existing template?
Jira provides templates for common project types, though the available choices can depend on your Jira plan and configuration. Choose the closest match to your team’s work, then review the workflow, issue types, and board before launch. A template is a starting point; it may still need careful adjustment to match your actual process.
Why can’t my teammates access the new project?
Project visibility and issue permissions may be limited to specific roles or people. Ask an administrator to review the project’s access settings and confirm that each teammate has the right role for their work. Test with a teammate account when possible, since seeing a project and being able to edit its issues are separate permissions.
Conclusion
Creating a Jira project starts with a few practical choices: select a fitting template, choose the right management style, set a recognizable name and key, then verify access and workflow. Test the project before inviting the full team so you can catch confusing settings early.
But here's the truth: a project that looks ready can still slow people down if its board, permissions, or issue types don’t match their daily work. Keep the initial setup focused, gather feedback after real tasks move through it, and adjust carefully. If your team needs another approach, ONES Project is a Jira alternative with flexible deployment and Jira-compatible workflows.