Jira users logging in this year will notice something different. The containers they have spent years calling “Projects” are now called “Spaces.” The items inside them, long referred to as “Issues”, are now “Work.” Atlassian began rolling out these changes in September 2025, completing the transition across all customer tiers by December. As of this month, it is fully live.
As Shilpa Airi, Principal Product Manager at Atlassian, said in the official announcement:
“Projects have a new name. Everything else is the same.”
The company is at pains to stress that nothing functional has changed. Workflows, automations, permissions, and data are all untouched. JQL and automation rules continue to accept “project” as a term behind the scenes. But for the millions of enterprise teams who have built their processes, documentation, and stakeholder language around Jira’s original terminology, the reaction has been pointed — and instructive about something bigger than a naming convention.
What changed and when
The rollout was staged by subscription tier. Free and Standard customers saw the change first, from 1 September 2025. Premium and Enterprise followed on 20 October. All remaining customers were transitioned by 10 November, with deferred release track customers, those on Atlassian’s stability-first update schedule, completing the transition by 9 December.
The April 6 Atlassian changelog confirms the change is fully bedded in, with further UI consolidation expected at the first Jira seasonal release on 5 May. “Project” will eventually be recognised in JQL searches as a synonym for “Space,” though Atlassian has not given a specific date for that addition.
Why Atlassian says it made the change
Atlassian gives three reasons in its official community announcement. The first is clarity. The word “project” implies a time-boxed initiative with a defined start and end. That does not reflect how most teams use Jira containers, which are persistent, ongoing hubs for a team or product area. “Spaces” is deliberately open-ended.
The second is consistency. Confluence has always used “Spaces” as its organising structure. Aligning Jira unifies the language across the Teamwork Collection — Jira, Confluence, Loom, and Rovo — as Atlassian pushes its connected platform narrative.
The third reason is the most strategically significant: differentiation. Atlassian simultaneously launched Atlassian Projects — a portfolio-level visibility tool in Atlassian Home, separate from Jira itself. It connects work across Jira Spaces, Confluence pages, and other tools. Leadership gets a high-level view of initiatives spanning multiple teams. With two distinct things sharing the name “project,” something had to change — and Atlassian changed the Jira container.
Jira Spaces vs. Atlassian Projects: Key Differences
- Jira Spaces: The day-to-day working container for a team or product; holds all tasks, backlogs, sprints, and work items; used by the people doing the work
- Atlassian Projects: A portfolio-level overview hub in Atlassian Home; aggregates work across Jira, Confluence, and other tools; aimed at leadership and stakeholders tracking initiatives
- Functionality: Spaces replace what were previously called Projects in Jira; nothing about configurations, workflows, or permissions has changed
- Audience: Spaces are for teams; Atlassian Projects are for executives and programme managers who need cross-team visibility without opening individual Jira boards
The reaction in the community
The community response is, to put it diplomatically, mixed. For teams that use Jira for time-boxed work with defined deliverables, fixed timelines, and external stakeholder reporting, “Spaces” simply feels like the wrong word. One user captured their frustration:
“I HATE THIS. These are not spaces, they are projects for us. Staff is confused, our clients are completely lost.”
Another raised the ecosystem overlap immediately:
“Very weird change. It will be a guessing game to figure out whether they’re talking about Jira or Confluence.”
For site administrators, the rename has introduced a specific operational headache. When a user now requests access to a “Space,” admins must determine whether they mean a Jira Space or a Confluence Space: two different systems, two different permission structures, now sharing identical language.
The rollout also exposed a live UI consistency problem. The Create button in some interface areas still reads “Project” while other areas show “Spaces.” One user described clicking Create and receiving “completely different options” depending on the path.
Integration concerns run separately. Atlassian says JQL, APIs, Forge apps, and automation rules remain unaffected. The term “project” continues to work in JQL for now. But the volume and specificity of community questions, covering smart values, REST API endpoint versions, and Forge compatibility, reflects real anxiety. Teams carry years of custom logic. One admin flagged the risk of “data corruption due to unannounced updates of automation smart values and REST API endpoint versions.” Atlassian needs a clearer answer on this before the May seasonal release.
The bigger strategic signal
Read in isolation, a terminology change is easy to dismiss. Read in the context of where Atlassian is heading, it is a clear statement of intent. Jira began as a developer tool, and “project,” “issue,” and “sprint” were native language for software engineering teams. “Spaces” and “Work” are deliberately more neutral — accessible to HR, marketing, operations, and finance teams who have never used a sprint board in their lives.
Atlassian is repositioning Jira as a general work management platform, competing directly with Monday.com, Asana, and ClickUp for the enterprise work management budget — not just the engineering toolchain. The launch of Atlassian Projects as a portfolio layer completes a structure that looks far more like a Monday.com architecture than a traditional developer tool: day-to-day execution in Spaces, strategic oversight in Atlassian Projects.
The timing is not accidental. Microsoft Project Online retires on 30 September 2026, and enterprise organisations are actively evaluating alternatives right now. Atlassian is clearly positioning itself as a credible landing spot for those customers — and it needs a language that resonates beyond engineering departments to make that case.
What enterprise teams should do now
The platform needs no action. But teams should not take that to mean the change has no impact. Send a short internal communication. Explain what changed and what did not. People logging into Jira and finding familiar labels gone will have questions — better to get ahead of them. Update training materials, onboarding docs, and governance frameworks that reference Jira terminology.
Admins running complex integrations should verify their custom JQL filters, Forge apps, and automation rules. Atlassian says everything works as before. Check it anyway. The April changelog is the right starting point for a full picture of what is live.
The first Jira seasonal release lands on 5 May. Atlassian has signalled further consolidation is coming. The Team ’26 event alongside it will likely bring more detail on the Spaces and Atlassian Projects roadmap. That is the next date to watch.
