Creating a Jira project sounds simple until the setup screen asks about project types, templates, permissions, and navigation. A rushed choice can leave your team with confusing workflows, missing fields, or access problems.
The frustration grows when everyone tracks work differently. Developers create tasks, managers need reports, and stakeholders struggle to see progress. A poorly configured project can slow delivery before work even begins.
But here's the truth: you can create a useful Jira project in minutes when you make a few decisions first. This guide walks you through each step, explains the available choices, and shows how to refine the project afterward.
How to Create a New Project in Jira
You can create a Jira project by opening the project menu, selecting Create project, choosing a suitable template, naming the project, and confirming its settings. Your Jira permissions determine which options appear.
- Sign in to Jira. Open your Jira Cloud or Jira Data Center account with project-creation permission.
- Open the project menu. Select Projects in the top navigation, then choose Create project.
- Select a project template. Pick Scrum, Kanban, bug tracking, task management, or another template that matches your workflow.
- Choose the project type. Jira may offer team-managed or company-managed projects, depending on your plan and permissions.
- Enter the project details. Add a project name, project key, and project lead when prompted.
- Review the configuration. Check workflows, issue types, access settings, and board preferences.
- Create the project. Select Create or Submit to finish setup.
- Add your first work item. Create an issue, assign it, add a due date, and place it on the correct board.
After creation, Jira usually opens the project overview or board. From there, you can invite teammates, adjust permissions, and customize the workflow.
Step 1: Confirm Your Jira Permissions
Jira only shows project-creation options to people with the required permission. A Jira administrator may need to grant you the Administer Jira permission or a related project permission.
If you cannot see Create project, ask your administrator to check your role. You may still create issues inside existing projects without permission to create new ones.
Step 2: Open the Project Creation Screen
Select Projects from Jira’s top navigation. Depending on your interface, you may see Create project directly or inside a menu labeled View all projects.
Jira’s menus can look different after interface updates. If the option is missing, use Jira’s search or ask an administrator to confirm your account access.
Step 3: Choose a Template
Templates provide starter workflows, issue types, boards, and reports. Your choice affects how the team records work and moves tasks toward completion.
A software team might choose Scrum for sprint planning. A support team may prefer Kanban because work arrives continuously and needs flexible prioritization.
| Template | Best fit |
|---|---|
| Scrum | Teams that plan work in fixed sprints |
| Kanban | Teams that manage a continuous flow of tasks |
| Bug tracking | Teams that investigate and resolve defects |
| Task management | Teams that need straightforward assignments and statuses |
| Project management | Teams coordinating milestones, dependencies, and deliverables |
Choose the closest match rather than trying to design everything from scratch. You can refine the project after your team understands its real workflow.
Step 4: Select Team-Managed or Company-Managed
Jira may ask whether you want a team-managed or company-managed project. This decision affects control, consistency, and administration.
Team-managed projects let individual teams configure workflows, fields, and statuses with less administrative support. They work well for smaller teams that need autonomy.
Company-managed projects use centralized schemes and shared settings. They suit organizations that need consistent workflows, reporting, permission controls, and governance.
| Project model | Useful when | Watch for |
|---|---|---|
| Team-managed | A small team needs fast, independent setup | Different teams may create inconsistent processes |
| Company-managed | Several teams need shared standards | Changes may require an administrator |
Step 5: Add the Project Details
Enter a clear project name that describes the team, product, or initiative. For example, Mobile App Support is easier to recognize than Project Alpha.
Jira usually creates a short project key. A key such as MAS produces issue identifiers such as MAS-24.
Keep the key short and recognizable. Changing it later can affect links, filters, integrations, and saved searches.
Choose a project lead who understands the work and can coordinate decisions. The lead does not need to approve every task.
Step 6: Finish the Setup
Review the project summary before confirming it. Check the name, key, lead, template, project model, and visibility settings.
Once you select Create, Jira builds the project with its initial board, workflow, issue types, and navigation pages.
The first setup is a starting point. Spend a few minutes testing the project before inviting a large group.
Which Jira Project Type Should You Choose?
The right project type depends on how your team plans, prioritizes, and completes work. The most important question is simple: does work move in sprints or continuously?
Scrum Projects
Scrum projects organize work into time-boxed sprints. Teams usually plan a backlog, select sprint work, hold regular reviews, and inspect completed items.
For example, a product team may plan two-week sprints. The board helps members see which stories are ready, active, blocked, or complete.
Choose Scrum when the team benefits from sprint goals and regular planning cycles. Avoid it when priorities change several times each day.
Kanban Projects
Kanban projects move work through a continuous workflow. A typical board includes To Do, In Progress, Review, and Done.
A marketing team handling campaign requests may use Kanban. New work enters the queue whenever it arrives, then moves forward as capacity becomes available.
Kanban works especially well when limiting active work matters. A team might allow only three tasks in review at once.
Business and Task Projects
Business project templates support general work such as operations, hiring, finance, events, and internal requests. They usually require fewer software-specific fields.
Task management suits teams that need assignments, due dates, priorities, and progress tracking. It can be a practical starting point for a small department.
How to Configure the New Project Correctly
Once the project exists, configure only what the team needs. Excessive customization creates maintenance work and makes reports harder to compare.
Set Up Issue Types
Issue types describe the kind of work being tracked. Common examples include tasks, stories, bugs, epics, and service requests.
Use names that match your team’s language. A design team may prefer Creative Request, while an engineering team may use Story or Bug.
Too many issue types create uncertainty. If two types follow the same workflow, combine them unless reporting requires a distinction.
Review Statuses and Transitions
A status describes where work is in the process. A transition describes how an issue moves between statuses.
A simple workflow might use To Do, In Progress, Review, and Done. Add Blocked only when the team will actively monitor it.
For example, an issue should not reach Done merely because someone stopped working on it. Define what completion means before changing the workflow.
Configure Components, Versions, and Labels
Components can group work by area, such as mobile, payments, or authentication. Versions can represent releases or planned delivery points.
Labels provide flexible grouping, though uncontrolled labels become difficult to maintain. Agree on naming rules before everyone starts adding them.
A useful label might be customer-impacting. Variations such as customer-impact and customer_issue weaken reporting.
Set Permissions and Visibility
Decide who can view, create, edit, assign, transition, and administer issues. Keep access aligned with the project’s sensitivity.
A public internal project may allow broad viewing. A project involving employee relations or commercial negotiations may need restricted access.
Test access using a regular team account. Administrators often see more than ordinary members, so an administrator’s view may hide permission problems.
How to Add People and Start Working
Invite the people who will actively manage work first. A smaller pilot group can identify confusing fields and permissions before the entire organization joins.
Add Project Members
Open the project’s settings and find the people, access, or roles area. Add team members to roles such as administrator, member, developer, or viewer.
Assign the least access needed for each role. A viewer may need progress visibility, while a project administrator may manage settings.
Create the First Issue
Select Create and choose the project. Add a concise summary, useful description, priority, assignee, and due date.
For example, write Confirm Android payment failure on version 3.4 instead of Payment issue. Specific summaries make search and reporting easier.
Build a Practical Backlog
Add only work the team can understand and prioritize. Each issue should explain the expected result, context, and next action.
Break large initiatives into smaller issues. A request such as Launch customer portal may need separate work for design, authentication, testing, and release preparation.
Check the Board
Move one test issue across the board. Confirm that each column matches a real step in the team’s workflow.
If the board shows five active tasks but the team can handle only two, use a work-in-progress limit. This exposes bottlenecks before they become delivery delays.
ONES.com as an Alternative Project Management Platform
Jira is powerful for teams that need issue tracking, agile planning, and detailed workflow controls. Some teams prefer a simpler project workspace with broader business planning features.
ONES.com provides an alternative environment for organizing projects, tasks, collaboration, and delivery planning. It may suit teams that want project management across product, design, engineering, and business work.
Capabilities to Consider
- Task and issue tracking: Create work items, assign owners, set priorities, and monitor progress.
- Agile planning: Organize backlogs, sprints, stories, and delivery goals.
- Roadmap planning: Connect larger initiatives with milestones and planned outcomes.
- Team collaboration: Keep conversations, updates, and decisions connected to active work.
- Requirement management: Capture needs and relate them to implementation tasks.
- Test management: Plan test activities and track quality work alongside development.
- Progress visibility: Use dashboards, views, and reports to understand project health.
- Workflow customization: Adapt statuses and processes to match the way your team operates.
Consider ONES.com when your team wants a unified project environment. Compare permission controls, integrations, reporting, migration effort, and pricing before switching platforms.
A practical evaluation uses one real initiative. Recreate a small workflow, invite several team members, and measure how quickly they can plan and update work.
Common Mistakes to Avoid
Many Jira problems begin during setup. A few simple checks can prevent weeks of confusion.
Choosing a Template by Name Alone
A template’s label does not explain every workflow decision. Open its details and review the included issue types, statuses, reports, and board behavior.
If a support team selects Scrum without sprint planning, members may spend time maintaining ceremonies that do not help their work.
Creating Too Many Custom Fields
Every extra field adds another decision for the person creating an issue. Keep fields that support action, ownership, prioritization, or reporting.
For example, a required field called Business impact helps triage. A required field called Additional context category may create unnecessary friction.
Giving Everyone Administrative Access
Broad access can produce accidental workflow changes, inconsistent labels, and permission gaps. Use project roles to separate administration from daily participation.
Skipping a Trial Issue
A test issue reveals problems quickly. Create one, assign it, transition it, add a comment, and confirm that the intended people can see it.
Common Challenges
I Cannot See the Create Project Option
Problem: Your account lacks the required Jira permission, or an administrator has limited project creation.
Solution: Ask a Jira administrator to grant the appropriate permission or create the project for you. Include the proposed name, key, lead, template, and visibility level.
I Chose the Wrong Project Template
Problem: The board or workflow does not match how your team handles work.
Solution: Review the project settings and simplify the workflow first. If the structure is fundamentally wrong, create a controlled replacement and move work carefully.
Team Members Cannot View or Edit Issues
Problem: Project roles, permission schemes, or issue security settings restrict access.
Solution: Test the project with an affected account. Check browse, create, edit, assign, and transition permissions separately.
The Board Does Not Show Expected Issues
Problem: The board filter may exclude issues by status, assignee, component, or another condition.
Solution: Review the board filter and confirm that each issue belongs to the project. Check whether the issue status maps to an active board column.
The Workflow Has Become Too Complicated
Problem: Extra statuses and transitions make work difficult to understand.
Solution: Ask the team to describe the actual process in plain language. Remove steps that do not change ownership, decisions, or visibility.
FAQs
Can anyone create a Jira project?
No. Jira normally limits project creation to administrators or people with the appropriate global permission. If you cannot find the creation option, contact your Jira administrator. You can give them the project name, key, lead, template, project model, and visibility requirements. They can create the project or adjust your role.
Should I choose a team-managed or company-managed project?
Choose team-managed when one team needs fast configuration and independent control. Choose company-managed when several teams need consistent workflows, permission schemes, reporting, or shared standards. Consider future growth as well. A small team may begin with team-managed settings, while a regulated organization may need centralized administration immediately.
Can I change the project key after creation?
Jira may allow project key changes, depending on your permissions and configuration. However, changing the key can affect issue links, integrations, saved searches, automation rules, and external references. Choose a durable key before creation. Use a short abbreviation that still makes sense to people who will read issue identifiers.
What should I name my Jira project?
Use a name that clearly identifies the team, product, service, or initiative. Examples include Customer Support Operations, Mobile Checkout, and Website Redesign. Avoid vague names such as Project One. A clear name helps people select the correct project when creating issues.
Can I create multiple boards in one Jira project?
Yes, Jira can support multiple boards that use different filters or planning views. For example, a product team might use one board for sprint delivery and another for high-level triage. Keep filters understandable and avoid creating separate boards for minor personal preferences. Too many boards make it harder to identify the team’s primary workflow.
How long does Jira project setup take?
A basic project can take only a few minutes to create. A useful production setup may take longer because you need to review permissions, workflows, issue types, board filters, and reports. Start with a simple configuration, test it with a few issues, then refine it after the team has used the project for real work.
Conclusion
Creating a Jira project is straightforward when you choose the workflow before clicking through the setup screens. Select a suitable template, pick the right project model, define clear access, and test one complete issue.
But here's the truth: the creation button is only the beginning. A project becomes useful when its statuses, fields, permissions, and board reflect how your team actually works.
If setup complexity is slowing your team, compare Jira with alternatives such as ONES.com. The best choice is the platform that helps people understand priorities, update progress, and finish work consistently.
