Jira Project Settings: A Practical Setup Guide for Teams
Are Jira settings slowing your team down? This practical Jira project settings guide helps you configure projects with less friction. Read now to learn how.
A Jira project can look ready while its settings quietly create extra work. Teammates may see the wrong issues, follow inconsistent workflows, or miss updates because permissions and notifications were never reviewed.
That friction grows as projects add people, issue types, and approval steps. A small configuration choice can affect how work gets assigned, reported, and completed. And if every project is set up differently, even experienced teammates need time to find their way around.
Here’s the truth: you don’t need to customize everything. You need to understand the key Jira project settings, choose options that fit your team, and test the result before inviting everyone. This guide walks you through that setup in a practical order, highlights common mistakes, and explains how to keep your configuration useful as the project changes.
A practical setup sequence for Jira project settings
Start by confirming the project type and your access level. Then configure only the settings your team needs to manage work clearly and securely.
- Open the project settings. Open your Jira project and select Project settings in the project sidebar. The label or location may vary slightly by Jira version.
- Check whether the project is team-managed or company-managed. This affects which settings you can change and how they are managed. Team-managed projects let project administrators control many settings locally. Company-managed projects often rely on shared Jira configurations maintained by Jira administrators.
- Set a clear project identity. Review the project name, key, description, and access level. Choose a key teammates can recognize, such as “WEB” for a website team, and describe what work belongs in the project.
- Review issue types and fields. Keep the issue types that match your work, such as tasks, bugs, and stories. Add fields only when they help someone make a decision or take action.
- Check workflows, screens, and permissions. Confirm that the steps in each workflow match how work actually moves. Make sure people can see and update the issues relevant to their roles.
- Test with a real example. Create a sample issue, move it through its workflow, and check whether the right people can view and update it. Adjust confusing settings before rolling out the project.
The order matters. For example, there’s little value in polishing a dashboard before confirming that the team can access the issues it needs to report on.

Choose the right project type before customizing
Jira’s project type affects how much configuration happens locally and how much depends on shared administration. That choice shapes what you can adjust later, so check it before investing time in detailed changes.
Team-managed projects
Team-managed projects are often a good fit when one team needs to configure its own work. Project administrators may be able to adjust workflows, issue types, and fields without changing settings shared across other projects.
For example, a small design team could create a review step that applies only to its project. The trade-off is that separate projects may develop different conventions if each team makes decisions independently.
Company-managed projects
Company-managed projects can use shared schemes and configurations. This can help an organization keep workflows, permissions, and issue fields consistent across several teams.
That structure also means some changes require a Jira administrator. Before requesting a change, check whether it could affect other projects that share the same configuration.
How to decide
Consider who should control project changes and whether other teams need the same setup. A single team with distinct steps may value local control, while a group of related teams may benefit from shared conventions.
You might be wondering: can you change project types later? Options vary by Jira product and configuration, so check the current project’s available actions before assuming a conversion is possible. Plan carefully if the project already contains active work.
Configure the settings that shape daily work
Project settings should make work easier to understand and complete. Begin with the choices that affect every issue, then move to features the team uses less often.
Project details and access
Use a recognizable name and project key, and write a short description that explains the project’s purpose. Set access deliberately, especially if the project includes private planning or customer information.
For instance, a public product backlog may need broader visibility than a project tracking a confidential launch. Review access with the project owner instead of assuming the default matches your team’s needs.
Issue types, fields, and screens
Issue types help people distinguish different kinds of work. Fields collect useful details, while screens control which fields appear when someone creates, edits, or views an issue.
Keep the issue creation form focused. If a bug report needs an environment and reproduction steps, include those fields. Avoid making every field mandatory when people cannot answer it at the start of the work.
Components, versions, and notifications
Components can group work by area, such as “Payments” or “Mobile app.” Versions can help teams track planned releases. Use these features when they support real ownership or planning, rather than adding categories nobody maintains.
Notifications also deserve a quick review. Too many alerts can encourage people to ignore them, while too few may leave assignees unaware of important changes. Test a typical issue update to see who receives a notification.
Align workflows and permissions with how work happens
A workflow should reflect the steps your team actually uses, not an ideal process that people bypass. Sketch the path on a whiteboard first, then match Jira statuses and transitions to it.
For a support team, that path might be Open, In progress, Waiting for customer, and Resolved. A software team might need review and testing steps instead. The useful workflow is the one teammates can follow consistently.
Keep transitions understandable
Use status names that make sense to people doing the work. Check what happens when an issue is reopened or moved back for changes. If a transition has a condition or approval requirement, explain it to the people who need to use it.
Give people the access they need
Permissions determine who can browse, create, edit, assign, or administer project work. Match those abilities to actual responsibilities. A contributor may need to update issues without having permission to change project-wide settings.
Here’s why: broad access can make accidental changes more likely, while overly restrictive access creates delays. Test access with accounts representing different roles, such as a project lead and a regular contributor.
Test the configuration, then maintain it
Before inviting the full team, walk through a realistic piece of work. Create an issue, assign it, update its fields, move it through the workflow, and check the resulting notifications and reports.
For example, ask a teammate to submit a bug report without your help. If they cannot tell which issue type to choose or which fields matter, simplify the form or add a short instruction.
Check reports and boards
Boards and reports depend on the way issues are organized. Confirm that the team can see the work it expects, and that statuses or fields support the reports it uses in planning meetings.
A team tracking releases might check whether its versions and issue statuses produce a useful release view. If the report requires manual cleanup each week, review the underlying configuration before adding more reporting steps.
Review settings as the project changes
Project needs change when a team grows, adopts a new approval step, or reorganizes its work. Schedule a brief review after major changes, and remove settings that no longer serve a clear purpose.
The best part? A small, regular check can prevent a major configuration overhaul. Ask teammates where they get stuck, then make targeted adjustments and test them with a real task.
A project management alternative: ONES.com
ONES.com is a unified platform for project management and knowledge management, powered by AI through ONES Assistant. ONES Project handles project management and is a Jira alternative; ONES Wiki provides knowledge management as a Confluence alternative. They are sold separately.

Teams comparing project platforms may consider ONES Project when they need structured work management and deployment flexibility. It offers Cloud, On-Premise, Private Cloud, and Air-gapped deployment options, with full feature parity between cloud and self-hosted versions.
Core capabilities
- Pain: Teams want to keep familiar Jira processes. ONES Project supports Jira-compatible workflows. Result: Teams can carry recognizable process patterns into a different platform.
- Pain: Shared configurations make changes difficult to manage. Custom workflows and fields let teams shape processes around their work. Result: Issue tracking can reflect the steps and details a team actually needs.
- Pain: Sprint planning feels disconnected from daily execution. Sprint management supports planning and tracking work in iterations. Result: Teams can connect planned work with progress during the sprint.
- Pain: Project leads need visibility into progress. Built-in reporting gives teams ways to review project activity. Result: Leads can follow work without relying only on status meetings.
- Pain: Repetitive steps consume time. Automation can handle selected recurring actions. Result: Teams can reduce manual updates where a consistent rule applies.
- Pain: A team needs to control where its platform runs. ONES.com offers cloud and self-hosted deployment choices, including air-gapped environments. Result: Organizations can select an operating model suited to their infrastructure requirements.
- Pain: Multiple add-ons increase configuration overhead. Native capabilities cover workflows, fields, sprints, and reporting. Result: Teams may reduce reliance on plugins for supported needs.
- Pain: A team wants to try the platform before a broader rollout. The free plan supports up to 30 seats. Result: A team can evaluate its project setup with a limited group first.
Application scenarios
A software team could use ONES Project to manage backlogs, sprint work, custom issue fields, and recurring workflow actions. Jira-compatible workflows may help when the team wants familiar process patterns while evaluating another platform.
An organization with restricted network requirements could assess its On-Premise, Private Cloud, or Air-gapped deployment options. A team that also needs knowledge management can consider ONES Wiki separately from ONES Project.
Common setup challenges and practical fixes
- Challenge: The settings menu does not show the option you need. Your access level or project type may limit available changes. Fix: Ask a Jira administrator to confirm your permissions and whether the project uses a shared configuration.
- Challenge: The issue creation form feels overwhelming. Too many fields make it harder to submit useful work. Fix: Keep essential fields visible and remove or make optional fields that people rarely know at creation time.
- Challenge: Teammates skip workflow steps. The process may not match their real work or status names may be unclear. Fix: Ask where the workflow breaks down, simplify confusing steps, and test the revised path with an active task.
- Challenge: Notifications become background noise. Alerts may go to too many people or trigger too often. Fix: Review notification rules with the team and keep alerts tied to updates that require attention.
- Challenge: A shared setting change affects another project. Company-managed projects may share configuration. Fix: Check which projects use the same scheme and coordinate changes with their administrators before editing.
Frequently asked questions
Where do I find Jira project settings?
Open the project and look for Project settings in its sidebar. The location and available options can vary with the Jira version, project type, and your permissions. If the menu is missing or an option is unavailable, ask a Jira administrator to confirm your access. You may have project-level permissions without the global or shared configuration permissions needed for a particular change.
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 can use shared schemes and configurations, which can support consistency across several projects. The right choice depends on who should manage changes and whether teams need the same workflow or fields. Check your Jira edition and project requirements before choosing, since features and management options may differ.
Can I change Jira project settings without being an administrator?
Some changes may be available to project administrators, while others require a Jira administrator. This is especially common when a project uses shared workflows, permission schemes, or other configurations. If you cannot edit a setting, identify the exact change and explain its effect on the team. An administrator can then confirm whether the setting is local or shared and make the adjustment safely.
Which settings should I configure first?
Start with project access, issue types, required fields, workflow steps, and permissions. These choices affect whether people can find, create, and move work through the project. Afterward, review notifications, components, versions, boards, and reports according to your team’s needs. A sample issue is a useful test: follow it from creation to completion and note every confusing step.
How often should I review project settings?
Review settings when the team changes its process, adds a new group, or finds recurring friction. A short check after a major project change can catch mismatched permissions, unused fields, and outdated statuses. You can also ask teammates to flag problems during regular planning. Avoid changing settings without a clear reason, especially when shared configurations may affect other projects.
Conclusion
Useful Jira project settings help your team find work, understand its next step, and access the information it needs. Start with project type and access, then configure issue types, workflows, permissions, and notifications. Test the setup with a realistic task before inviting everyone.
When settings create friction, pause and identify the specific problem before adding more customization. A focused review can make project work clearer and reduce avoidable administration. If your team is comparing platforms, ONES Project is one Jira alternative to evaluate alongside your workflow and deployment requirements.