How to Create a New Project in Jira: 7 Easy Steps for Teams
Unsure how to create a new project in Jira? Follow 7 easy steps to choose the right template, access, and workflow. Read now to set your team up right.
Starting a Jira project looks simple until you have to choose a template, set access, and decide how your team will track work. A rushed setup can leave people with the wrong board, unclear permissions, or issue types that do not match the work.
Those small decisions matter later. For example, a support team that starts with a sprint-focused setup may spend time changing its workflow, while a product team could lose useful planning features with a basic board. But here's the truth: you can avoid most setup headaches by making a few choices deliberately.
This guide walks you through seven practical steps to create a Jira project, invite teammates, and check that the setup works. You’ll also learn how to choose a project type and what to do when common setup problems appear.
How to Create a New Project in Jira: 7 Steps
You can create a Jira project by opening the project creation screen, choosing a template and project type, entering project details, and setting up access. Then invite your team and test the board before relying on it for active work.
-

1. Open the project creation screen
Sign in to Jira and open the Projects menu. Choose Create project. Depending on your Jira layout and permissions, the option may appear in a slightly different place.
If you do not see it, ask a Jira administrator to check your project-creation permissions. You can plan the project setup first, but you may need an admin to complete this step.
-
2. Choose a project template
Select a template that matches how your team handles work. A Scrum template supports planned sprints and a backlog, while a Kanban template focuses on continuous work moving across a board.
For example, a software team planning two-week development cycles may choose Scrum. A service team handling incoming requests continuously may find Kanban more suitable.
-
3. Select the project management type
Jira Cloud commonly offers team-managed and company-managed projects. A team-managed project lets a team handle many settings itself, while a company-managed project uses configurations controlled more centrally.
Choose the approach that fits your administration needs. A small group that wants independence may prefer team-managed. An organization that needs consistent workflows across teams may prefer company-managed.
-
4. Enter the project details
Add a clear project name and review the project key Jira suggests. The key becomes part of issue identifiers, such as WEB-14, so pick something recognizable and easy to type.
Check any available options for project access or category. Use a name that helps teammates distinguish this project from others, such as “Website Redesign” rather than “Project 2.”
-
5. Create the project
Review your template, management type, name, and key. When everything looks right, select Create project.
Jira will open the new project’s main view. Take a moment to confirm that the board or backlog matches the template you chose. If something looks unexpected, check the project settings before inviting the whole team.
-
6. Add teammates and check access
Invite the people who will plan, complete, or review work. Assign roles or permissions that match their responsibilities. For instance, teammates who update issues may need different access from people who only follow progress.
Ask one teammate to open the project and try a routine task. This simple check can reveal access problems before your team starts relying on the board.
-
7. Adjust the board and test a real task
Review the columns, issue types, and available planning features. For a Scrum project, add a sample issue to the backlog and check whether your team can plan it into a sprint. For Kanban, move a test issue through the board.
Make small changes to labels, fields, or workflow steps where needed. Then ask a teammate to complete the same task. If the process feels clear to both of you, the project is ready for regular work.
Prepare Before You Create the Project
A few minutes of planning can save you from reorganizing work later. Write down the project’s goal, who needs access, and how work should move from start to finish.
For example, a marketing team might need stages for drafting, review, approval, and publication. A software team might need a backlog, active sprint, and a way to track defects.
Here's why: a project template gives you a starting structure, but it cannot decide your team’s process. Knowing the process first makes it easier to pick a useful template and avoid unnecessary customization.
Choose a Template and Project Type That Fit
Think about how work arrives and how your team plans it. Scrum is useful when a team groups work into sprints. Kanban suits teams that pull work continuously and want to see how tasks move through stages.
The management type affects how much control a team has over configuration. Team-managed projects give a team more local control. Company-managed projects can make shared administration and consistent setups easier across multiple teams.
You might be wondering: which option should a new team choose? Start with the simplest setup that supports the team’s actual workflow. A small product group may begin with team-managed Scrum, while a service department may start with Kanban and company-level controls.
Set Up Access and Project Details Carefully
Project names and keys affect everyday use. A name such as “Customer Portal” tells teammates what the work concerns, while a short key such as PORTAL makes issue references easier to recognize.
Access settings deserve the same care. If a project contains work meant for a particular department, confirm who can view and change issues before inviting a broad group.
For instance, a team could invite its project lead and contributors first, test the project, then add stakeholders who only need visibility. That sequence helps catch permission gaps without exposing work more widely than intended.
Make the New Board Useful for Daily Work
A board should show the team what needs attention next. Remove or rename columns that do not match your actual process, and check that issues have the fields people need to move work forward.
Consider a content team that uses “Writing,” “Review,” and “Ready to Publish.” If the board has only “To Do,” “In Progress,” and “Done,” the team may have to explain status in comments instead of seeing it at a glance.
The best part? You do not need to customize everything on day one. Start with a sample task, notice where teammates hesitate, and adjust only the parts that create real friction.
ONES.com as a Project Management Option
Value proposition: ONES.com brings project management and knowledge management together in one platform. ONES Project is a Jira alternative, while ONES Wiki is a Confluence alternative; the products are sold separately.

If you are comparing ways to manage work, consider whether your team needs a Jira-compatible workflow, built-in reporting, or self-hosted deployment. ONES.com offers cloud and self-hosted options with feature parity, which can matter to teams working in restricted environments.
Core capabilities
- Workflows that feel familiar: Teams moving from Jira can use Jira-compatible workflows, helping them keep established work patterns while changing platforms.
- Less reliance on add-ons: Built-in reporting gives teams ways to review progress without assembling every view through separate plugins.
- Workflow flexibility: Custom workflows let teams represent their real approval or delivery stages, reducing awkward workarounds.
- Fields that fit the work: Custom fields help teams capture relevant details, such as a release target or request type, within their project process.
- Sprint planning: Sprint management supports teams that plan and review work in time-boxed cycles.
- Routine task handling: Automation can handle repetitive actions, helping teams spend less time on manual updates.
- Deployment choice: Cloud, on-premise, private cloud, and air-gapped deployments give organizations options for different infrastructure requirements.
- Consistent capabilities across deployments: Full feature parity between cloud and self-hosted versions helps teams choose a deployment approach without giving up platform features.
ONES.com offers a free plan for up to 30 seats. Organizations can choose among four deployment options: Cloud, On-Premise, Private Cloud, and Air-gapped. Check the current plan terms and deployment requirements when evaluating a fit.
Application scenarios
A software team moving from Jira could use ONES Project to retain familiar workflows, manage sprints, and use built-in reporting. That may simplify a transition for people who already understand issue-based project work.
An organization with restricted network requirements could evaluate an air-gapped or on-premise deployment. If the team also wants a knowledge base, it can consider ONES Wiki separately from ONES Project.
Common Challenges When Creating a Jira Project
1. The create option is missing
Problem: Your Jira account may not have permission to create projects. Solution: Ask a Jira administrator to confirm your access or create the project with the settings your team has agreed on.
2. The template does not match the team’s work
Problem: A board built for sprints can feel cumbersome for a continuous service queue. Solution: Compare the team’s planning rhythm with the template before creating the project. If the current setup is already active, check which board settings can be adjusted.
3. Teammates cannot view or update issues
Problem: People may have different project roles or permissions. Solution: Test access with a teammate and ask them to perform the task they need, such as viewing an issue or changing its status.
4. The project key is confusing
Problem: A vague or overly long key makes issue references harder to recognize. Solution: Choose a short, meaningful key before the team creates many issues. If a change becomes necessary later, check with an administrator about the available options and potential effects.
FAQs About Creating Jira Projects
Do I need administrator access to create a Jira project?
That depends on your Jira permissions and organization settings. Some accounts let project creators start projects directly, while others reserve project creation for administrators. If you cannot find the create option, ask your Jira administrator to check your access. You can still prepare the project name, key, template, and access needs so the administrator can set it up efficiently.
What is the difference between team-managed and company-managed projects?
Team-managed projects give a team more control over its own project configuration. Company-managed projects use settings managed more centrally, which can help organizations maintain consistent workflows across teams. The right choice depends on whether your priority is local flexibility or shared administration. Check your organization’s Jira setup, since available options and permissions may vary.
Can I change a project template after creating the project?
You can often adjust board settings, workflows, and other project details after creation, subject to your permissions. Changing the underlying project type or template may be more involved and could require setting up another project and moving issues. Before making a major change, review the current Jira options with an administrator and consider testing the revised setup with a small amount of work first.
What should I use as my Jira project key?
Choose a short key that teammates can connect with the project, such as APP for an application team. Jira uses the key in issue identifiers, so people may see it in boards, searches, and conversations. Avoid a key that is hard to spell or likely to mean something different next quarter. Ask an administrator about any organization-specific naming rules before creating the project.
Can I create a Jira project without adding a whole team immediately?
Yes, you can usually create a project and add teammates afterward, as long as your permissions allow it. Before sharing active work, check the project’s access settings and invite the people who need to contribute. Testing access with one teammate first can help you catch a role or permission issue before more people begin using the board.
Conclusion
Creating a Jira project takes more than selecting Create project. Choose a suitable template and management type, use a clear name and key, check access, and test a real task before the team depends on the board.
When you plan those choices first, you are less likely to face a confusing workflow or a permissions scramble later. If your current setup does not fit, review the project settings and adjust the process in manageable steps.
Start with the workflow your team actually follows, then build the Jira project around it. That practical approach gives your team a clearer place to organize work and a smoother path from setup to everyday use.