So since we are no longer getting any response here @Josh Sherwood should we just interpret that as Atlassian, as usual, do not care about the customer and their feedback and will just push this crazy change no matter what? We are just talking to ourselves at this point?
@Terry Tyson you should go ask your Space Management team in your company's Space Management Office. They can create you a Space Charter and a Space Management Plan.
We do have teams that use Jira projects to house multiple project to manage, and sometime that would confuse some individuals. However, those types of projects were far less common and the majority of people understood it was a Jira project that contained projects.
I could see renaming Jira Projects to something like Workspace(s) like someone mentioned earlier might not be a bad idea, but using the same name as Confluence is going to cause far more confusion for users than the "project of projects" situation. I really do wish there was a permanent opt-out feature. Our company would absolutely not implement this change.
I recall that in many demos presented at Summits/Teams, Atlassian would use a fictional "Space Company" to show off new Jira and Confluence features. So clearly Space has been on their minds for quite some time.
When I was trying to find some of those demos, Google actually led me to this:
Back on April 1 2022, they announced that they would be launching one of their employees into space to work remotely for a week. Even though he experienced extreme distress, anxiety, and outright rejection (of stomach contents), they "shot him into space, regardless".https://www.atlassian.com/blog/space
Truly some important lessons learned back then. ;-}
Apologies, Andriy. It appears that some UI references to 'project' were missed during the updates. Thanks for highlighting these, I've passed it on to the team and they'll be fixed shortly.
@Josh Sherwood Should I take that as a sign that the Atlassian team at Atlassian doesn't know that "some UI references to 'project' were missed during the updates"? They renamed something randomly and "missed" a hundred of other places? Or, maybe there was just one person who worked on that, and then they went on vacation in the middle of the task, and no one else cared? This sounds silly, I know, but what else can I think after such a bad renaming job and such communication? I mentioned in the original comment that there are tons of places where renaming didn't happen yet, and my examples are just that - examples of a bigger problem. And, guess what, fixes for those cases that you passed to the team, they didn't happen.
A professional team would have developers that would do the renaming job thoroughly, in ALL the places (or, almost all, humans do make mistakes, that's fine). A professional team would have a QA team that wouldn't let this through. A professional team would have a release/delivery manager that wouldn't let this through (even if the first 2 teams fail). It is very sad that Atlassian team working on that change is not like that.
You gained a lot of extra trust from customers and partners with this one. Good job.
Renaming Projects to Spaces, adding Teams when we already had Groups, (and maybe even renaming Summit to Team?). It was right there all along in the training materials they've been using for years!
These were clearly the clues about all these changes. We just needed to read between the lines!
That's from Confluence 7.19 docs, but below is their Plan from 2013. Wait, I mean their Board. But not their Dashboard. And definitely not their Roadmap, or Portfolio, or Advanced Roadmap:
I mean, not to blame Scott since he's not there anymore, but, I'm pretty sure he's the one viewing this board!
Kind of weird how we have Teams in Spaces, not in one single Space. Maybe that'll be next month.
86 comments