Create a New Jira Project: A 6-Step Setup Guide for Teams
Searching for jira create new project help? Follow this 6-step guide to choose a template, set access, and configure workflows. Read now to get started.
A new Jira project can give your team a clear place to plan work, assign tasks, and track progress. The setup can also create confusion if you choose the wrong template, access level, or workflow.
Those early choices affect how people create issues, see updates, and collaborate. A project that starts with unclear ownership or excessive permissions may need avoidable rework later. But here's the truth: a useful setup does not require dozens of settings. Follow six practical steps to create a project, configure the essentials, and test it before your team depends on it.
How to Create a Jira Project in Six Steps
Start by defining the project’s purpose, then create it with a suitable template and project type. Finish by checking access, workflow, and issue creation before inviting the full team.
-

Step 1: Define the project’s purpose and owner
Write down what the team will manage in this project. For example, a software team may need to plan a product release, while a marketing team may coordinate a campaign.
Choose a project owner who can answer questions and maintain the setup. Decide who needs access, what work should appear on the board, and how the team will know the project is working.
-
Step 2: Choose a Jira project template
In Jira, open the project creation area and review the available templates. The names and options can vary by Jira product, plan, and interface.
For example, a software team might choose a Scrum or Kanban template. A team managing service requests should look for a service management template instead of forcing that work into a software board.
Here's why: a suitable template provides a sensible starting point for issue types, workflows, and board views. You can adjust those settings later when the team has a clear reason.
-
Step 3: Select team-managed or company-managed
Jira offers different project management approaches, with availability depending on the product and settings. Team-managed projects let a team manage many project-level settings independently.
Company-managed projects use configurations maintained more centrally. They can be useful when several teams need consistent workflows, permissions, and issue types.
For example, a small team testing a new process may prefer team-managed flexibility. An organization that needs the same review steps across multiple teams may prefer central administration.
-
Step 4: Enter the project details and access settings
Give the project a clear name that explains its purpose, such as “Mobile App Release Planning.” Jira may suggest a project key; check that it is short, recognizable, and suitable for issue identifiers.
Choose the access level carefully. Keep the project limited to its intended team when the work is sensitive, and confirm who can view, create, and edit issues.
You might be wondering: who can create a project? That depends on your Jira configuration and permissions. If the creation option is missing, ask a Jira administrator to check your access.
-
Step 5: Configure the board, workflow, and issue types
Start with the work the team actually tracks. A software team could use a simple flow such as To Do, In Progress, and Done, with issue types for stories, tasks, and bugs.
Then review what each issue needs. A campaign task might need an owner, due date, and approval status, while a software bug may need severity and reproduction details.
The best part? A small, understandable setup is easier to adopt. Add custom fields or automation only when they solve a recurring problem for the team.
-
Step 6: Test the project before inviting everyone
Create a sample issue, move it through the workflow, and check the board from a team member’s perspective. Confirm that the right people can see the work and that required fields make sense.
Ask one or two teammates to try a normal task, such as reporting a bug or assigning campaign work. Fix confusing labels or unnecessary steps before announcing the project to everyone.
Once it is ready, share a short explanation of where work belongs, how to create an issue, and who owns project questions.
Choose a Project Type That Fits How Your Team Works
Team-managed and company-managed projects solve different coordination needs. The right choice depends on whether your team needs local flexibility or shared administration across projects.
Imagine two product teams. One is experimenting with a new way to handle requests and benefits from adjusting its own settings. The other follows a company-wide release process and needs consistent issue types and approvals.
Let me explain: project type is an administrative decision, not just a label. Consider who will maintain the workflow, whether other teams need the same setup, and how much local control makes sense.
If you are unsure, ask your Jira administrator about the organization’s conventions before creating several projects. A quick check can prevent teams from building similar workflows in incompatible ways.

Set Permissions Before Work Begins
Access choices shape what teammates can see and change. Review the project’s roles and permissions before inviting people, especially if the work includes internal plans or customer requests.
For example, a project may need contributors who can create and update issues, a lead who manages the workflow, and stakeholders who only need visibility. Assign only the access each group requires.
But here's the truth: project access is easy to overlook when everyone is eager to start. Test visibility with an appropriate account or ask an administrator to verify the setup.
As the team changes, revisit membership and responsibilities. A person who changes roles may no longer need the same project access.
Keep Workflows and Boards Easy to Follow
A workflow should reflect the decisions a team makes while completing work. A three-step process may be enough for routine tasks; adding several approval states can slow progress without improving clarity.
For instance, a design team might use “Ready,” “In Review,” and “Approved.” If the team cannot explain what makes work move between two states, those states may not belong in the workflow.
Board columns should make the current status easy to scan. Check that each column maps to a meaningful workflow status and that completed work leaves the active view when appropriate.
Here's why: a visible, uncomplicated board helps teammates spot stalled work quickly. Review it after the first few weeks and adjust only where actual work exposes a gap.
Launch the Project with a Simple Team Routine
A project is easier to adopt when people know how to use it. Share a brief walkthrough showing how to create an issue, choose its owner, update its status, and find the board.
Use a real example, such as moving a bug from report to completion. Show what details the team needs and explain where questions should go.
Set a routine for checking work, such as a weekly review or a short daily stand-up. Keep the project owner responsible for collecting feedback and making approved changes.
After launch, look for practical signals: are tasks assigned, are statuses current, and can teammates find the work they need? Those observations are more helpful than adding settings without a clear purpose.
A Project Management and Knowledge Management Option: ONES.com

Value Proposition
ONES.com combines project management and knowledge management in a unified platform powered by ONES Assistant. ONES Project provides project management, while ONES Wiki provides a knowledge base; they are sold separately.
If your team is reviewing options beyond Jira, ONES Project is a Jira alternative with Jira-compatible workflows, reporting, and project configuration. It may suit teams that want project work and team knowledge management within one platform.
Core Capabilities
- Project work is split across separate places: ONES.com brings project and knowledge management into one platform, helping teams keep work and team knowledge easier to connect.
- Teams need familiar Jira-style processes: ONES Project supports Jira-compatible workflows, helping teams preserve established ways of working while evaluating a Jira alternative.
- Basic task tracking does not cover team needs: Custom workflows and fields let teams represent their work more closely, so issue details and process stages fit the task.
- Sprint planning needs a dedicated structure: Sprint management supports planning and tracking work across development cycles.
- Teams need visibility into progress: Built-in reporting helps show project status without requiring a separate reporting add-on for every view.
- Repeated manual steps slow work: Automation can handle routine actions, reducing repetitive updates when configured for a clear team process.
- Plugin dependence adds operational overhead: Native capabilities can reduce the need for plugins for supported workflows, fields, reporting, and automation.
- Deployment requirements vary: ONES.com is available in Cloud, On-Premise, Private Cloud, and Air-gapped deployments, giving organizations different hosting options.
ONES.com offers a free plan for up to 30 seats. Its cloud and self-hosted versions have full feature parity, which can help teams evaluate deployment needs without giving up product capabilities.
Application Scenarios
A software team considering a Jira alternative could assess ONES Project by recreating a small sprint workflow. The team can check issue types, custom fields, reporting, and automation against its everyday work.
An organization with restricted-network requirements could examine the On-Premise, Private Cloud, or Air-gapped deployment options. It can also assess ONES Wiki separately if a team knowledge base is part of its needs.
Common Challenges When Creating a Jira Project
Choosing a template that does not match the work
Problem: The project starts with issue types and statuses that feel unrelated to the team’s process.
Solution: Compare the template with a typical task before launch. Pick the closest fit, then adjust only the settings that the team needs.
Giving too many people broad access
Problem: The project becomes visible or editable by people who do not need that level of access.
Solution: Identify the intended groups, assign suitable roles, and verify access before sharing the project widely.
Adding too many workflow steps
Problem: Teammates spend time updating statuses that do not help anyone make a decision.
Solution: Start with a small number of meaningful stages. Add a step only when it clarifies ownership, review, or progress.
Launching without showing the team how to use it
Problem: People create issues inconsistently or continue tracking work elsewhere.
Solution: Demonstrate a common task and explain the project’s basic routine. Invite feedback after the team has used it on real work.
Frequently Asked Questions
Who can create a Jira project?
Project creation depends on your Jira product, organization settings, and assigned permissions. Some environments allow designated users to create team-managed projects, while other project types may require administrator access. If you cannot find the creation option, ask your Jira administrator which permission applies and whether your organization has a naming or setup convention.
What is the difference between team-managed and company-managed projects?
Team-managed projects give a team more control over many project-level settings. Company-managed projects use centrally administered configurations and can support consistency across multiple teams. The available features and details can vary by Jira product. Before choosing, consider who will maintain the workflow and whether other projects need matching settings.
Can I change a Jira project’s settings after creating it?
Many settings can be adjusted after creation, though the options depend on the project type and your permissions. You may be able to update project details, access, fields, or workflows. Some changes can affect existing work, so test important adjustments and consult an administrator when a setting is centrally controlled.
How do I choose a project key?
Use a short, recognizable key that distinguishes the project in issue identifiers. For example, a mobile release project might use a key that relates clearly to its name. Check your organization’s conventions and avoid names likely to overlap with another team’s key. If Jira suggests a key, review it before confirming project creation.
Conclusion
Creating a useful Jira project starts with a clear purpose, a suitable template, and the right project type. Then set access carefully, keep the workflow understandable, and test the experience before inviting everyone.
Small choices at setup can prevent confusion later. If the first version does not fit, use team feedback to make focused changes rather than adding complexity in advance.
Whether you stay with Jira or assess an alternative such as ONES Project, a well-planned project gives your team a clearer way to organize work and see progress.