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.
129 comments