Evolving Jira terminology: ‘Projects’ will soon be ‘Spaces’

[Nestor Rodriguez Perez]

And so the "good" ideas continue, specially if nobody asked for it.

So, why not change "Jira" for "Billy"?

[Kate]

So happy about this terminology change! Our users find the term "Projects" really confusing (generally those who work on BAU work, not Projects) so we're already use the term "Project Space" with our users to avoid confusion.

[tradian]

I've been calling it workspaces because projects confused people the way we used it at my org. I like Spaces!

[Josh]

@Shilpa Airi - We now have "work items" in "projects. What if we had "work items" in "workspaces"? Workspaces are where you work on your work items.

This minor naming tweak would help disambiguate Confluence spaces and Jira spaces.

@tradian's comment got me thinking about this...

[Peter Norris]

A very welcome change! We're trying to break the mindset of everyone wanting a new Jira Project for every initiative; this is really going to help with the comms.

[Stephen_Lugton]

We've been trying to get more of our business teams using Jira and Jira Service Management for both new work (without referring to them as projects) and BAU, and changing the name away from projects will help with getting by in from those teams.

@Shilpa Airi as @tradian and @Josh suggest, workspaces might be a better terminology than spaces; Confluence uses spaces, and that's the space where you write your documentation, so having Jira use workspaces aligns with that's where you do your work.

[Matt Smith]

Introducing a Nightmare for everyone - the constant question of are you talking about Jira or confluence !


Can we have something useful like reports that can be seen in the customers portal !

[Wurm Peter]

So in 2, 3 years we have spaces that contain work items and pages all together?
I guess that is where this is headed.

[Sameer Kamat]

Thanks! When will JIRA users be called "astronauts" as they navigate the galaxy of tasks and tickets!

[roydbrayshay]

__ Jimi Wikman I'm with you that words matter and that these terms become overloaded causing confusion. I do think that the term Epic was first coined in Kent Beck's XP Explained book published in 2001 and it was defined there as a large story. Many people still think of it that way. In the same book a "theme" was defined as a group of stories and many still use that terminology also. I appreciate there are many different ways to control and manage software projects but I was particularly referring to agile teams here and I think that's where these terms are rooted and commonly used.

[Linda Hoff]

I am also wondering about the APIs. Will they be impacted or not?

[David Wuth]

I wish Atlassian would spend more time on useable features, instead of renaming existing stuff...

And, really? Spaces? This will result in the same confusion around "Teams" and how there is not really one Team. Now we have two types of Spaces.... groan.

[Wurm Peter]

We won't have two types of "spaces" for long. Sooner or later they will be merged.

Positive change as jira projects often don't resemble real projects.

[David Wuth]

@Wurm Peter Spaces will always be separate. Jira and Confluence cannot be merged.