You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi @Helen OBoyle, (sorry, they shut down the other page so I couldn't reply there, which is a shame as there was another conversation I wanted to respond to as well)
Apologies, I hadn't considered that situation (where unsupported software isn't approved for use). If you/we can persuade them to revert back to making the legacy editor their key editor, then more the better, however I don't think they are going to do that. My aim was more 'if they are no longer working on it, then they could at least leave it running so some people can still use it'.
I was trying to offer damage limitation suggestions, not satisfactory solutions, as I don't think there are any that they are going to consider.
I was hoping that they'd respond to that suggestion, and possibly show some inclination towards it, in which case we'd have a platform to argue for a level of support that would work for companies like yours.
Ultimately, I suspect they are going to blunder through the next few months and then at some point just switch off the old editor. I hadn't seen the articles about the new underlying storage format, which indicates that bigger changes might be afoot.
Whatever they do, I hope you manage to get through it with a minimum of disruption!
Thanks for the reply! I'm a bit miffed about them closing down the other thread, particularly as there were a couple of conversations between people going on that didn't necessarily include Atlassian...
I agree with what you are saying there. I was trying to work out an option for them to keep the old one running while still developing the new one, and was hoping to inspire this kind of discussion to almost crowdsource a solution for them, but by shutting it down they kind of nipped that one in the bud. Like, there has to be a level of support that they can offer for the old editor that balances out the customers they might lose.
There is surely a way that they can keep the older editor running until the new editor is up to speed. I tried to use Cloud to author materials for this release and it just hasn't worked out well. With the old editor, I could have made a decent go of it.
I'm not really sure where we go from here though. Like you said, everything they're doing feels like they're trying to rush people off the old and onto the new. And it does feel like it's aimed at the casual user. We've commented, emailed, focus grouped, ticket-raised, but none of it has given me any confidence that they are listening.
They're giving us a round hole and leaving it up to us to make our pegs fit, and they don't seem too concerned whether we succeed or not.
@Helen OBoyle - I did not see that you had started this new page, and I created https://community.atlassian.com/t5/Confluence-Cloud-discussions/NEW-Try-out-the-new-editing-experience/td-p/1222198 when I saw that Atlassian had shut down the comments on https://community.atlassian.com/t5/Confluence-discussions/Try-out-the-new-editing-experience/td-p/1000813
@Helen OBoyle , @Tom Crowley -- I think that the only way to continue the discussion from before is to @... mention any previous commentor/responder. Then hopefully they will get attached to this discussion.
Oops, and then there were two! I only saw this post after I'd commented on your page. I'd say stick with yours just for the name - easier to find maybe?