Understanding the Transition From Jira Projects to Jira Spaces

Atlassian is undergoing a significant strategic shift in its product terminology. Starting in late 2025, the familiar "Jira Projects" are being rebranded as "Jira Spaces." This change is not merely cosmetic; it reflects a broader evolution in how teams across the globe organize work, moving away from rigid, time-bound definitions toward more flexible, continuous environments.

The primary confusion for most users stems from the fact that "Spaces" has historically been a term reserved for Confluence. Now, with Jira adopting the same nomenclature, understanding the nuances between a Jira Space, a Confluence Space, and the newly introduced "Atlassian Projects" is essential for any organization relying on the Atlassian ecosystem.

The Short Answer: What is Changing?

Jira Projects and Jira Spaces are effectively the same thing within the context of the Jira interface. A Jira Space (formerly known as a Jira Project) is the fundamental container for your work. It is where teams manage issues, tasks, bugs, and user stories. It houses the workflows, permissions, and boards (Scrum or Kanban) required to execute daily operations.

The terminology update is a phased rollout. By the end of 2025, the word "Project" will be replaced by "Space" across all Jira Cloud products, including Jira Software, Jira Service Management, and Jira Product Discovery.

Jira Space vs. Confluence Space: Tasks vs. Knowledge

The most immediate question for long-time users is how a Jira Space differs from a Confluence Space. While they now share a name to provide a unified user experience, their functional purposes remain distinct.

The Operational Container: Jira Space

A Jira Space is designed for action and execution. It answers the questions: What needs to be done? Who is doing it? What is the current status?

• Primary Units: Issues (tasks, bugs, stories).
• Core Function: Tracking the lifecycle of work through a defined workflow (e.g., To Do -> In Progress -> Done).
• Visuals: Boards, backlogs, and roadmaps.

The Knowledge Container: Confluence Space

A Confluence Space is designed for documentation and collaboration. It answers the questions: Why are we doing this? What is the historical context? How is this feature designed?

• Primary Units: Pages and blogs.
• Core Function: Storing long-form content, meeting notes, project requirements, and technical specifications.
• Visuals: Hierarchical page trees and document templates.

In a mature workflow, these two spaces act as a pair. A Product Manager might write a requirements document in a Confluence Space, which then links to specific tasks inside a Jira Space where developers track their progress.

Jira Space vs. Atlassian Project: The New Layer of Confusion

Adding to the terminology shift is the introduction of "Atlassian Projects" (accessible via Atlassian Home). This is where the term "Project" has been moved to a higher organizational level, creating a clear distinction between day-to-day work and high-level initiative tracking.

An Atlassian Project serves as a "wrapper" that provides visibility into the big picture. It allows stakeholders to see progress across multiple Jira Spaces without needing to dive into the technical details of individual tickets.

Why the Rename? The Strategic Logic Behind "Spaces"

Atlassian’s decision to move away from "Project" is driven by three main factors:

1. Inclusivity for Non-Technical Teams

The term "Project" implies a beginning and an end. However, many teams use Jira for ongoing operations—such as IT support (JSM), marketing campaign management, or HR onboarding—that never truly "finish" in the traditional sense. "Space" is a more inclusive, open-ended term that better describes a continuous workspace.

2. Unified Teamwork Collection

Atlassian is positioning its products (Jira, Confluence, Loom, Rovo) as a "Teamwork Collection." Standardizing terminology makes the platform more intuitive. When a user moves from Confluence to Jira, they are moving between two different types of "Spaces" within the same unified environment, reducing the cognitive load required to navigate the tools.

3. Avoiding Conflict with High-Level Portfolio Tools

By reclaiming the word "Project" for the high-level Atlassian Project tool, the company can offer a clearer hierarchy. A "Project" now represents a significant business initiative, while a "Space" represents the workspace where the actual work happens.

Technical Impact: Will Your Jira Instance Break?

For Jira administrators and developers, the most pressing concern is whether this change will break existing integrations, scripts, or filters. Atlassian has confirmed that this is a UI-only change.

JQL (Jira Query Language)

Your existing JQL filters will not break. Even though the UI says "Space," the JQL syntax project = "Project Name" will continue to function. Atlassian is introducing a "space" alias, allowing you to use either project or space in your queries for backward compatibility.

APIs and Webhooks

The REST API endpoints will remain unchanged for the foreseeable future. The internal identifiers and data structures that refer to "project" will stay as they are to prevent global infrastructure failures for third-party apps and custom integrations.

Automation and Smart Values

Automation rules using the {{project.key}} or {{project.name}} smart values will continue to work perfectly. There is no immediate requirement to rewrite your automation library.

Rollout Timeline for 2025

The transition is being managed in stages to allow organizations to adapt. Below is the projected schedule for the terminology update:

• September 2025: Rollout begins for sites on Free and Standard plans. Most sites in this tier will see the change completed by late September.
• October 2025: Rollout begins for Premium and Enterprise plans. This usually follows major industry events like Atlassian Team '25 Europe.
• November 2025: Target for 100% rollout across all standard cloud instances.
• December 2025: Organizations on Release Tracks (who opt to bundle and delay changes) will see the update applied.

Note: This change currently applies only to Jira Cloud. There are no confirmed plans to bring this terminology change to Jira Data Center at this time.

Preparing Your Team for the Shift

While the functional impact is zero, the cultural and documentation impact can be significant for large organizations. Administrators should consider the following steps:

1. Update Internal Documentation: If you have internal wikis or onboarding guides that use "Project" screenshots and terminology, begin auditing them for updates.
2. User Communication: Send out a brief internal announcement clarifying that "Projects" are now "Spaces" but their work items (tickets) and boards haven't moved.
3. Search Habits: Remind users that when they use the "G + G" keyboard shortcut or the global search bar, they should start thinking in terms of "Spaces" to find their work containers.

Summary

The transition from Jira Projects to Jira Spaces represents Atlassian's vision of a more unified and inclusive digital headquarters. By aligning terminology with Confluence and creating a separate layer for Atlassian Projects, the ecosystem becomes more structured for complex, cross-functional work.

• Jira Space is where you do the work (tasks).
• Confluence Space is where you document the work (knowledge).
• Atlassian Project is where you report on the work (status).

This terminology change is a sign of Jira’s maturity as it expands from a software development tool into a universal platform for all teams.

FAQ: Frequently Asked Questions

Can I opt-out of the change to "Spaces"?

No. This is a global UI update implemented by Atlassian across all Cloud sites. There is no administrative toggle to revert to the "Project" terminology.

Does this change affect Jira Service Management?

Yes. Jira Service Management (JSM) "Projects" will also become "Spaces." For example, a "Service Project" will likely be referred to as a "Service Space" or a "Service Management Space" within the UI.

Will the Project Key (e.g., "PROJ-123") change?

No. The Project Key—the prefix used for your issues—remains exactly the same. It is a permanent identifier that will not be renamed to "Space Key" or altered in any way that affects ticket links.

Is Jira Data Center getting this update?

As of late 2025, Atlassian has stated there are no immediate plans to change the terminology in the Data Center (on-premise) version of Jira. This change is exclusive to the Cloud ecosystem.