Jira Review 2026: Free Limits, Pricing & Workflows

Free includes up to ten users, unlimited work items/spaces, and 2GB file storage. That can support a meaningful pilot without deleting old issues to satisfy a record ceiling. The Free-plan restrictions matter just as much: space permissions, roles, and work-level security cannot be customized. On a site that has always been Free, users with Jira access administer Jira spaces. That is a space-level permission statement, not a claim that every user becomes an organization administrator.

Downgrading an existing paid site is a different scenario: configured permissions can remain but cannot be edited under Free. Do not use a screenshot from that downgraded account as proof that a fresh Free site can configure the same controls. Free also has community support and a 100-notification-email daily limit. Administrative audit logs are unavailable when all Jira apps on the site are Free; automation execution logs are a different feature and should not be substituted for the site's administrative audit history.

For a five-person team, governance can trigger an upgrade sooner than headcount. If contractors must not see sensitive work or client records need controlled visibility, test the actual rule rather than assuming a small free plan is inherently safe. Our free project-management guide provides the wider shortlist, while Linear vs Jira compares the different limits directly. Choose a plan only after the intended roles can work without accidental access or reliance on an administrator bypass.

The Atlassian rate card lists monthly Jira Standard at $9.05 for each of the first hundred users, and Premium at $18.30. Higher bands have different marginal rates. The pricing calculator can open at a larger headcount and show a blended per-user average, such as the 300-user selection. Treat the selected quantity as part of the quote. Multiplying a rounded average back into a supposedly exact invoice introduces another error.

Annual pricing instead buys a whole user band. The listed Standard 1-10-user band is $900 per year, and Premium is $1,850. Five Standard users held at the monthly rate for twelve months cost $9.05 times five times twelve, or $543 before extras; ten cost $1,086. The annual band can therefore be more or less attractive depending on utilization. This is arithmetic from the rate card, not a universal annual-discount recommendation. Run the same calculation at today's headcount and the next likely band boundary.

Monthly subscriptions use maximum-quantity billing: a mid-cycle addition can increase charges, while removing users does not create a matching immediate credit for that same period. Licensed access, not activity in the tool, determines the relevant population. Review dormant accounts and contractor access through an approved process, not by deleting useful work history. Add security, Marketplace, and usage charges separately using the SaaS spending guide. The base Jira subscription is only one line of the operating budget.

Atlassian distinguishes team-managed and company-managed spaces. Team-managed configuration is isolated to that space; company-managed spaces can share administrator-controlled schemes. The choice affects consistency, autonomy, and who changes the process. It is not enough to say one is simple and one complex. A group with several delivery teams may need shared controls, while a small experiment may not justify centralized administration for every status change.

Start with one actual workflow: incoming work, triage, ready, in progress, review, and accepted. Decide who can move each transition and whether an important field must be present. Then test an exception such as a blocked issue, an urgent bug, or a task reopened after release. Avoid reproducing every status from an old spreadsheet merely because Jira can configure it. More states can create reporting ambiguity when two teams use the same label for different outcomes.

Pair the workflow with responsibilities outside the tool. Who maintains templates, decides when a field is obsolete, and reviews inconsistent use? The small-team PM guide supplies adoption criteria, while ClickUp and Asana offer alternative work models to evaluate. A configurable system earns its cost when the organization actually needs and maintains those controls; otherwise it can become a record of unnecessary ceremony rather than useful coordination.

The plan guide lists Standard's 250GB storage, expanded permissions, and data-residency capabilities. Premium adds cross-team Plans, dependency/capacity planning, sandboxes, release tracks, and unlimited storage. Release tracks govern when Atlassian cloud updates reach your site, not your product's deployment approvals. Choose Premium for a demonstrated requirement, not merely because the team has grown. Standard may cover a small team's private-work needs while a separate cross-team planning requirement justifies Premium.

Planning requires reliable inputs. Build a proposed evaluation containing two teams, a dependency, a realistic capacity constraint, and unfinished work at the end of an iteration. Inspect what changes when an owner is absent or an estimate moves. A roadmap view does not prove the plan is feasible, and capacity tools do not repair inconsistent estimates. Compare Linear's review for another product-delivery model, and keep Notion separate when the primary need is long-form context rather than controlled execution.

Premium's 99.9% SLA is a contractual availability commitment with defined scope and exclusions. The SLA terms cover specified browser experiences, exclude sandboxes, and include a claim process; they are not proof that every API, plugin, mobile action, or page meets a performance target. Document which business activity needs continuity and what happens during interruption. Vendor availability credits are not a substitute for an incident owner or an export and recovery plan.

The current automation-usage guide measures executed steps and describes pooling contributions across an organization's apps/sites. Jira Standard contributes 400 steps per user per month, Premium 750, and Enterprise 1,000. A trigger, condition, and two executed actions are four steps, not one flow. Some no-change or error outcomes can count too. Do not use an older successful-rule-run allowance as if it describes the current meter.

Free requires a clear caveat: the dedicated meter guide and pricing page describe 150 steps per subscription, while a general official usage FAQ calls it per user. Confirm the allowance displayed for the actual account rather than silently resolving that conflict in the more generous direction. Announced extra-usage billing at $0.50 per 1,000 additional steps begins December 3, 2026 in the reviewed documentation. That is future-dated relative to this review, not an extra charge we observed on an October invoice.

Rovo usage is a separate credit system. Standard, Premium, and Enterprise contribute different per-user allowances pooled at organization level; Rovo-powered steps use Rovo credits rather than also consuming automation steps. Included AI does not mean unlimited agent work. Review extra-usage controls, activation requirements, and the announced billing start with an administrator. If n8n or Zapier participates in the same workflow, price its execution separately and prevent one integration's retries from unexpectedly multiplying actions in another.

For Jira Standard and Premium, Atlassian Guard Standard is a separate security subscription to evaluate for SAML SSO and SCIM. Enterprise includes Guard Standard, not every Guard Premium capability. Eligible unique users across supported apps and sites determine the relevant population, so that bill may not equal the size of a single engineering team. A requirement for centralized identity management belongs in the initial quote, not a surprise discovered after the migration.

Marketplace billing can also follow the licensed host population rather than only the people actively using an extension. Price a required time-tracking, testing, or reporting add-on at the applicable licensed quantity and check its data ownership separately. A useful marketplace is a capability route, not evidence that every missing feature is bundled free. Our software evaluation framework helps keep mandatory add-ons distinct from optional experiments.

Keep service support, product discovery, and development execution separate in the purchasing model. A team can integrate a customer-support platform with Jira issues without assuming it has purchased Jira Service Management, and it can plan delivery without treating Product Discovery as a free Premium tab. Name each product, licensed role, and owner. This prevents a comparison built around Jira's base price from quietly promising an entire Atlassian product portfolio.

The Jira export documentation distinguishes issue data and a site backup that can include media. Backups do not automatically cover third-party app data; automation configurations need separate treatment. Since January 22, 2026, Backup Manager only restores backups thirty days old or less under the documented policy. Keeping an older export does not prove that facility can restore it. Inventory users, custom fields, comments, links, files, apps, permissions, and the intended restore mechanism before scheduling a cutover.

Linear's Jira migration guide illustrates the risk: custom fields do not import, and non-image attachments can remain URLs pointing back to Jira. An import can appear successful while important context becomes inaccessible after Jira is retired. Test a representative epic, subtasks, required fields, a private issue, an image, and a document attachment. Match record counts and retrieval rights, then retain source access until those files and histories remain usable independently.

Use the Linear vs Jira comparison when the move is between these two products; it separates an import from ongoing synchronization. More generally, migrate a small authorized sample first, record how statuses and identities map, and make rollback responsibilities explicit. Do not claim a lossless migration because titles and descriptions look correct. The team must demonstrate usable ownership, permission, history, and file behavior before the new workflow can replace the old one.

The 8.6 editorial assessment reflects Jira's documented work-tracking, shared-administration, planning, and ecosystem capabilities, balanced against Free governance constraints, multiple cost models, and migration responsibility. It is not an independently measured uptime or productivity result. Jira is worth shortlisting when meaningful workflow controls and relationships justify its administration. A simpler team should first establish that it needs those controls rather than assuming more configuration creates better delivery.

Evaluate Free with its actual restrictions, Standard for required access and operational controls, and Premium for demonstrable cross-team planning or sandbox needs. Compare Linear for a more opinionated product-delivery model and Trello for a simpler board-shaped job. Record the final headcount, billing cycle, identity requirement, automation allowance, and exit plan. A maintained process with clear ownership is more valuable than either a crowded settings page or a low starting price.