Greg, I want to like this just for the level of effort. Naming is also some of the most difficult abstractions, so I'd grant that.
However, the main issue is that the "unit" boundary where permissions are generally based having the same name will always create confusion.
In other words, had they started calling Jira Projects something else, like Jira Tranches, I'd say marketing has failed but you get used to it over time. Changing it intentionally to line up as the same thing as Confluence boggles me.
I'm in that late stage approach of just acceptance as well. I wish we weren't encumbered by this dinosaur, but it's what we have.
Atlassian Team members are employees working across the company in a wide variety of roles.
December 2, 2025 edited
Hi @Spencer Hudson Thanks for reaching out, and I apologise for the hassle while we update all our materials. I've checked with the team that looks after those learning docs, and these should be all updated and completed by the end of January.
Just a thought, maybe next time you decide to rename something that is so heavily entrenched in documentation, maybe you might wanna prepare the updated documentation first, then release the change.
@Rafa Yep.. We came from ClickUp this year because it was no longer serving its purpose (Our PM was a huge CU fan so it was why we ended up on it) but when they left, we made the transition to Jira due to it kind of being a standard for our industry (software).
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
@Terry Tyson They've said it at least once in this thread - they want Jira to be for more kinds of teams and less daunting to less technical users, so instead of leaning into what makes them valuable to software companies, they're making themselves indistinguishable from the rest of the pablum.
Thanks for sharing your concerns Andriy. I apologise for any inconvenience caused by the missed UI references. The team is actively auditing for any oversights, and will be fixing these soon. Thanks again for your feedback.
May I ask what is your definition of "soon"? "Projects" are still all around the place - in UI, in the online documentation. I noticed no changes. "Space" and "Project" are randomly used everywhere, often on the same page, like this
"The team is actively auditing for any oversights" is obviously not true.
In the case of putting estimates on kanban cards (7265) we're about to enter it's about to turn 13 years old. They said they'd review it in 2018 but it may take 12 months. It's an absolute joke.
Any timeframe is simply placating you without saying "no, naff off we do it our way". Under no circumstance do I have any faith in their timeframes. They may be the reason the joke about having "by Christmas" means you ask "which Christmas" exists.
139 comments