How to get feedback heard about degraded user experience and usability of Jira after 2025 Changes

[Shanmuga Narayanan Pitchaipillai]

With the forced terminology changes of Jira Software Projects to Spaces - Causing enormous confusion among large corporate users who look for stability and standardization in their management tools , how do we get our feedback heard to the Atlassian product designers and User Experience designers ? 

The forced structural change is causing considerable amount of confusion and causing distrust for Atlassian brand itself. 

[Shanmuga Narayanan Pitchaipillai]

a possible way to address , from what i could think off without knowing the details of designers have brought about these changes  , 

the confusion that is getting created between what is a Jira Software Space vs what is a Confluence Space vs what is a Jira Projects which is being used for goals i believe is overwhelming for many of the non technical users - i have tried to champion the use of Jira within my company , but with this dizzying pace of user experience changes and terminology changes is causing distrust of the platform itself for many of my endusers.

If jira wanted to create a grouping of different projects and products like confluence a team or workspace user may want to align together they could have simply created a additional layer of "Spaces" at parent level grouping for Jira Software projects and Confluence spaces and any other atlassian products in use at that "Spaces" - Workspace level , which would have atleast made sense for me to convey to the end users how to read this.

The abrupt forced change of Jira Software "Projects" - "Spaces" is so very confusing and has been causing enormous distrust among users creating pain for anyone who is looking to promote Jira usage in large corporations 

[Arkadiusz Wroblewski]

Hello @Shanmuga Narayanan Pitchaipillai  and @Bisharat Ullah Khan 

As I understand you both, I can relate to why Atlassian made this change even if I’m not personally happy about it. We have to live with it, because Atlassian provides great tools. In the end, the naming is mostly cosmetic.

The main reason was the introduction of Atlassian Projects. What Jira used to call “Projects” were never really projects in the classic sense; they were more like work-management containers/spaces.

Atlassian Projects = big-picture initiatives used to consolidate and track work across multiple Jira spaces
Jira Spaces = the places where the actual work items (issues) live

I’m not "super" happy about it either, but the change is mostly cosmetic.

[Bisharat Ullah Khan]

best