I could be wrong, but I believe that Atlassian made a big mistake by forcing all users to use the Fabric editor and now instead of admitting to their mistake and going back to the old editor, they choose to bury their heads in the sand like an ostrich (which apparently ostriches don't do, but that's how the saying goes)
It would be interesting if Atlassian polled all users and asked a very simple question: do you prefer the old editor or the new editor? I would love to see that answer. My guess is that a *significant* number of users will say that they prefer the old editor.
Someone wrote here a few months ago that the Fabric editor seems to be geared for casual users, not technical writers. That makes sense to me. But what about all of us that write technical documentation and miss features found in the old editor?
Atlassian keeps ignoring our complaints. @[deleted] and @Tom Crowley were very eloquent and expressed what I believe is the pain of MANY (not just a handful of) users. It seems like "internalize" is a synonym for "ignore" at Atlassian.
Also, I wonder how many of the positive responses here are legitimate (from actual happy customers)
@Heidi Trevethan - whimsy is good and some of our spaces are full of hilarity, Python (Monty) references, Hitchiker's Guide quotes, Calvin and Hobbes (especially Spaceman Spiff!), and other silliness.
But having /giphy is useless fluff and insulting if it comes at the price of loosing the fundamental functionality we need to do the real, hardcore work of documenting, configuration managed (Comala Workflows) space mission procedures, data, V&V, etc... As I mentioned in a prior post, fortunately all that work is done on our Confluence Server sites which fortunately haven't been corrupted by the 'new experience' and which we will keep stable at their current versions. We had been using the Cloud site early during projects for development work which then was exported to the server site when it was stood up, but that is now essentially impossible.
Besides, we've got /giphy on our Slack channels where it's much more 'useful' to enhance casual communications...
"New world order with Drag n Drop!" +1 👍 AGREED! the ability to easily reorder and group pages in tree is awesome.
@Product Team: This Drag-n-Drop has however led to some 🤦♀️ accidental page moves... so please provide a confirmation notification (with UNDO command please!)
I think the most important things I am looking forward to are:
- Customisation for Jira Service Desk.
Currently, the page only takes up a third of the screen real estate. This makes Confluence pages, especially the New Editing Experience pages, squashed and ugly to look at. It would be good to have greater control over the look and feel of Jira Service Desk.
- Livesearch macro
Allowing logged-in and logged-out users to search using the livesearch macro is probably my most awaited feature.
It does seem to depend on your use case. For example I use "Expand" all the time and now adding a title to expands has gotten much easier. This has actually saved me a lot of time. Lots of little things like that in the new editor which I am happy with.
@Alex Alesio There is an undo option. It comes up and blocks the other pages I'm trying to move so I have to close it manually after moving each page. Does it not appear for you?
How about OneDrive integration to match Google Drive integration (and I don't mean with a 3rd party plug-in, I mean natively). OneDrive is very popular in the corporate world.
@Jessica Taylor I understand you are trying to put a good face on the battle of the Somme, but you, and all of Atlassian, comes across as incredibly tone deaf to the very real struggles that a significant portion of your customers are experiencing.
The fact that no Atlassian representative has addressed @Bob Sovers metrics on the sheer number of issues logged against the Fabric editor really says a lot about Atlassian's views on customer satisfaction.
For reference, I'm re-posting Bob's comments here:
If anyone is interested, here is a query that will pull up ALL of the public-facing Bugs and Issues in the Confluence Cloud product that are associated with the "Fabric Editor" : (currently 505)
It is interesting that for the entire time that the new editor has been in place, 505 bugs and issues were filed, and only 80 were fixed, answered, or deployed.
Here is the full breakdown:
Total files issues and bugs for Cloud Fabric Editor -- 505
Unresolved -- 363
Fixed -- 77
Won't Fix -- 6
Duplicate -- 44
Cannot Reproduce -- 5
Answered -- 2
Not a Bug -- 3
Tracked Elsewhere -- 2
Deployed -- 1
Won't Do -- 1
Incorrectly Filed --1
I guess that we should be thankful that none have the resolution "Unsolved Mysteries" (yes, that is a possible resolution!)
(Me again... I'm telling you that this is me again, Jeff, because the editor for these comments is broken and I cannot apply a Block Quote format to only part of the content!!! ) I really hope that next year's Atlassian Summit is going to address All of the the complaints and issues that we have all been generating for the last year. And not in a saccharine "we hear you but need to internalize your comments" way, but in a genuine "we've screwed up, had the best of intentions, but screwed up and we are actively taking on your use cases and you will see roll out of solutions in 6/9/12/24 months."
Look, we all know that development is hard and that sometimes, you get it wrong. Being wrong isn't a bad thing. It just gives you a chance to grow and learn and evolve. Sticking to your poor decisions in the face of overwhelming evidence that those decisions were the wrong ones is idiotic and short-sighted. We have governments for that.
Atlassian Team members are employees working across the company in a wide variety of roles.
December 13, 2019 edited
My name is Daniel and I'm a Product Manager on the Confluence Cloud team. Thank you all for your comments and feedback. We hear you loud and clear regarding comments in edit mode and I'm happy to share that we've prioritized this feature and we're actively working on designing and building a solution. Stay tuned as we'll have more to share on this in the coming months.
Community Managers are Atlassian Team members who specifically run and moderate Atlassian communities. Feel free to say hello!
December 13, 2019 edited
@Shannyn Johnson I am guessing @DA meant to post here because the topic of comments in edit mode was brought up there. You can see more of the editor roadmap here if you're interested.
Really disappointed in the changes made, obviously the Product team are not end users or Project Managers who understand the importance of documentation. If your Project is about as complex as a Christmas shopping list I'm sure you would love the features but unfortunately the new Editor but this needs some major work.
To say "Stay tuned as we'll have more to share on this in the coming months" confirms there is a distinct lack of user awareness in the Product team. For those who rely on this product on a daily basis, even a week is far too long for this to be re-mediated.
Next release cycle, unless we get budget approval for a real authoring tool, we're going to have to decide whether it's easier to author in Confluence or to do it in Word and import it.
155 comments