Jira Free Tier: Limits, Features, and Setup Guide for Teams

Wondering if Jira Free fits your team? Explore jira free tier limits, features, and setup—read now before you build your workflow.

Choosing a project tool can feel simple until your team hits a user cap, runs out of storage, or needs a workflow the free plan cannot support. The Jira free tier can give a small team a practical place to plan work, track issues, and coordinate sprints without a subscription fee.

But here's the truth: “free” comes with limits that can affect daily work. If you discover them only after inviting teammates or building a process around a feature, changing course takes time.

This guide explains what Jira Free includes, where its limits matter, and how to set up a project with room to grow. You’ll also find ways to keep a small team’s workflow manageable and signs that it may be time to consider another plan.

What the Jira free tier includes

The Jira free tier is Jira Cloud’s no-subscription plan for small teams, with core issue tracking and agile planning features for up to 10 users. It includes tools for managing backlogs, boards, sprints, and basic automation, alongside limits on storage and rule runs.

That can be enough for a startup tracking a handful of product tasks or a small operations team managing requests. The right fit depends on how many people need access and which capabilities your workflow depends on.

Jira product screenshot

Free plan limits at a glance

Area	What to expect	Why it matters
Users	Up to 10 users	Count everyone who needs access, including occasional contributors.
Storage	2 GB of attachment storage	Large screenshots and other attachments can use capacity quickly.
Automation	100 rule runs per month	Frequent or multi-step automation can use the monthly allowance.
Support	Community support	Your team may need to troubleshoot issues through community resources.

Plan details can change, so check the current Atlassian plan page before making a decision. The table gives you a planning baseline, not a guarantee that every detail will remain the same.

Features you can use for everyday project work

Jira Free supports common agile workflows, including Scrum and Kanban boards, backlogs, issue tracking, and sprint planning. Teams can also use reports and basic automation to see work progress and reduce repetitive updates.

For example, a small app team could create a backlog, assign bugs, and run a two-week sprint. A Kanban team could move support requests across columns such as “To do,” “In progress,” and “Done.”

How to set up Jira Free for your team

Start with one project and a simple workflow. A smaller setup makes it easier to see whether the free plan fits before you invite the entire team or build elaborate processes.

Create or sign in to an Atlassian account. Follow the Jira Cloud signup flow and choose the Free plan when prompted. Check that you are creating a Jira site for the team that will use it.
Choose a project template. Pick Scrum if your team plans work in timed sprints and uses a backlog. Choose Kanban if work moves continuously through stages.
Name the project around its work. For example, “Website Improvements” is clearer than “Project 1.” Keep the first project focused on a team or a defined workstream.
Invite only the people who need access. With a 10-user cap, confirm who needs to create or update issues. Agree on an owner for access as the team changes.
Set up a few issue types and workflow stages. Start with tasks, bugs, and a small number of status columns. Add custom fields only when the team can explain what decision each field supports.
Add current work and try a short cycle. Enter a few real tasks, set owners and priorities, and run a sprint or use the Kanban board for a week. Ask teammates where they get stuck before expanding the setup.
Review usage and activity. Check user access, attachment use, and automation runs regularly. This helps you spot capacity concerns while there is still time to adjust.

Here's why a small pilot helps: a team of six might discover that it needs a bug-triage step, while a team of ten may immediately need to plan around the user cap. A week of real work can reveal more than a complicated setup built in advance.

How to keep a small Jira project manageable

A free plan works best when the project stays easy to understand. Use a short set of statuses, give issues clear owners, and agree on what belongs in a task description. If a teammate has to guess whether an issue is blocked or simply waiting, the workflow needs clarification.

For example, a product team might use “To do,” “In progress,” “Review,” and “Done.” It can add a “Blocked” status if work regularly stalls, but adding several near-identical stages can make the board harder to maintain.

Use automation selectively

Automation can handle routine actions, such as assigning an issue when it enters a specific status. On the free plan, however, each rule run counts toward the monthly allowance. Reserve rules for work that saves meaningful effort, then check their usage.

A useful test is to compare the time saved with the rule’s activity. If a rule runs hundreds of times to save a few seconds each time, it may use capacity better spent on a more important workflow.

Keep attachments purposeful

With limited attachment storage, teams should avoid treating Jira as a catch-all for large media. Attach the screenshot or short reference that helps someone resolve an issue, and remove material that no longer supports active work.

If a design review requires many large images, agree on a separate place to store them and keep a link in the Jira issue. That keeps project work connected while reducing unnecessary storage use.

When Jira Free may stop fitting

Watch for recurring friction rather than one unusual week. A team approaching 10 users, regularly hitting storage capacity, or needing more automation may be ready to compare paid plans or other project workflows.

Consider a five-person team that adds contractors for each release. It may fit within the cap for most of the year, then have to choose between giving new contributors access and removing existing teammates. If that choice repeats, access restrictions are affecting the work.

Signs to review your plan

Your team regularly needs access for more than 10 people.
Attachment storage or automation usage frequently approaches its allowance.
You need more control over permissions, administration, or reporting than the Free plan provides.
Your team spends time maintaining workarounds instead of completing the work itself.
Support needs require a response path beyond community assistance.

You might be wondering: does reaching a limit mean you need to switch tools immediately? Not necessarily. First, check whether removing inactive accounts, simplifying automation, or trimming attachments resolves the issue. If the same constraint returns, compare the cost and effort of upgrading with the effort of changing platforms.

A Jira alternative for teams that need connected project and knowledge work

ONES.com is a unified platform for project management and knowledge management, powered by ONES Assistant. ONES Project is a Jira alternative for project and issue management; ONES Wiki is a Confluence alternative for team knowledge. They are sold separately, so teams can choose the product that fits their needs.

For a team evaluating Jira Free, the practical question is whether its current limits match the way the team plans work. ONES Project offers Jira-compatible workflows, sprint management, reporting, custom workflows and fields, and automation. It also supports cloud and self-hosted deployments, including On-Premise, Private Cloud, and Air-gapped options.

Where ONES Project may help

ONES.com product screenshot

Teams working around Jira’s plan limits: ONES Project offers a free plan for up to 30 seats, which may give a growing team more room before it has to rethink access.
Teams that need a familiar workflow: Jira-compatible workflows and sprint management can help a team carry over established planning habits.
Teams needing tailored processes: Custom workflows and fields let teams match issue tracking to the work they actually do, with less dependence on plugins.
Managers who need progress visibility: Built-in reporting helps teams review work without assembling separate status updates.
Teams automating repeat tasks: Automation can reduce manual updates and keep routine steps moving.
Organizations with deployment requirements: Cloud, On-Premise, Private Cloud, and Air-gapped deployment options give teams different ways to run the platform.
Teams that need self-hosting without a separate feature set: ONES.com states that its cloud and self-hosted versions have full feature parity.
Groups keeping project work and knowledge together: ONES Project and ONES Wiki cover project management and knowledge management within the ONES.com platform, while remaining separately sold products.

Two practical scenarios

A 12-person product team that has reached Jira Free’s user limit could evaluate ONES Project’s 30-seat free plan. The team can test its sprint workflow and reporting before deciding whether a move makes sense.

An organization that must keep project work within a restricted network could assess ONES.com’s On-Premise, Private Cloud, or Air-gapped deployment options. Its team should confirm technical and operational requirements before choosing a deployment.

ONES.com is one option to evaluate, not an automatic fit for every team. Compare the workflow, deployment needs, administration effort, and total cost against the constraints you experience today.

Common challenges when using Jira Free

Most problems come from planning around a limit too late. A few simple habits can make the plan easier to manage, especially when a team has a stable headcount and a focused workflow.

Problem: You reach the user cap. Review access periodically and remove accounts that no longer need project access. If active contributors still exceed the limit, compare an upgrade with a platform that accommodates your team.
Problem: Automation runs out before the month ends. Audit rules for unnecessary triggers, repeated actions, and rules that no longer support the workflow. Keep the highest-value automations active.
Problem: Attachments use storage quickly. Remove outdated attachments where appropriate and keep only the material needed to act on an issue. Link to approved team storage for larger assets.
Problem: The board becomes difficult to read. Reduce duplicate statuses and unclear issue types. Ask teammates to follow one shared definition of when work moves between stages.
Problem: No one knows how to resolve a plan issue. Assign a project owner to monitor access and usage. For support beyond community help, review whether a paid plan or another platform better meets the team’s needs.

Frequently asked questions

Is Jira Free really free?

Jira Free has no subscription charge while you remain on the Free plan. It does have limits, including a maximum of 10 users, 2 GB of attachment storage, and 100 automation rule runs per month. Review Atlassian’s current plan details before relying on a specific limit, since plan terms can change.

How many people can use Jira Free?

The Free plan supports up to 10 users. Count everyone who needs access, including contractors and occasional collaborators. If your active team grows beyond that limit, you can review paid Jira plans, adjust access where appropriate, or compare another project management platform.

Can I use Scrum and Kanban on the free plan?

Jira Free includes agile planning features for Scrum and Kanban workflows. A Scrum team can work with a backlog and sprints, while a Kanban team can track issues as they move through board columns. Choose the workflow that reflects how your team handles work rather than adding process steps for appearance.

What happens when a team reaches a Jira Free limit?

The effect depends on the limit and the current Atlassian plan terms. For example, a team may need to reduce the number of active users to stay within the user cap, or review how it uses storage and automation. Check the plan details in your Jira administration area and decide whether a workflow change or upgrade is appropriate.

Can I move from Jira Free to a paid plan later?

Teams can review and change their Jira subscription as their needs evolve. Before upgrading, identify the constraint you need to solve, such as additional users, administrative controls, or more capacity. Then compare available plans and confirm the current terms for your site.

Conclusion

Jira Free gives small teams a useful starting point for issue tracking, backlogs, boards, sprints, reporting, and basic automation. Its 10-user cap, 2 GB of attachment storage, and monthly automation allowance are important to consider before you build a workflow around it.

Start with one focused project, invite only the people who need access, and review how the team uses Jira after a short trial run. If limits repeatedly disrupt work, compare an upgrade with alternatives such as ONES Project, taking workflow fit and deployment needs into account.

The best choice is the one that lets your team plan and deliver work without spending too much effort managing the tool. A clear view of Jira Free’s features and boundaries helps you make that choice before the pressure builds.