Let me add one more thing, our functional requirements docs are 100-150 pages each with tables, text and images. We are now loading them without splitting the sections and the performance is terrible. This is a bad user experience all around.
I agree with many of the comments before me. The new import function has dropped in value for my team, as the ability to upload Word Documents and split by heading was an important step in many of our processes and procedures.
A two-minute job has now become a nightmare as we're having to physically upload over one-thousand individual pages.
For me, the new function serves as a 'copy and paste' set up, rather than a structured process.
I hope Confluence are taking this feedback on board and considering either reverting to the past process, or updating the new process to include the previous benefits and aspects.
We absolutely need the option to split Word docs by header. This function is the primary reason that we selected Confluence for our intranet. Since the Cloud can obviously support the split on existing Word docs that are migrated to the Cloud, why would you remove this option for those who need it.
The loss of this functionality is a huge problem for us.
We also need to be able to import Word docs to an existing page.
What is your suggestion for your customers who are heavy users of these functions?
Please respond. The loss of this function is holding up our conversion to the Cloud.
We just made a little 1 minute video on how to import a document into Confluence: https://youtube.com/shorts/juxT-cKDgJk Might be helpful for sharing with teammates.
This is a disaster. The documentation receives word input documents from the company pipeline, and it is HELL to import the content.
Importing a Word file that is 90+ pages (even if I split it into 3 smaller word documents) with alltogether cca 50 headings (on 3 levels) and several lists, nested lists, etc takes a week instead of a day. Thank you Confluence for not giving a rat's bum, and forcint the so-called development of the wiki product- so far I have seen only downgrades and unnecessary features added to your product in the past 4 years. I really regret standing up for picking your product back in the day when we had to choose between a 2000 USD structured tool license only one person can use, and this collaboration tool that used to be good in 2018.
We are nearing a year after this announcement, and still no sign of a solution. Anyone know of an alternative solution for importing documents split per heading level?
Maybe someone made an add-in to replace the broken standard functionality?
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 Leaders.
Hi @Geert Bellekens , since I am suffering a lot from the deletion of this functionnality :'( , I am using a workaround to import my word documents splitted by heading. I described it here. Hope it can help you :) !
I agree with the complaints about not being able to split by H1, H2, H3 etc. I used this functionality to prove the value of Confluence to an entire organization. It was helpful for creating site structures, site templates and in knowledge management artifact creation. This 'upgrade' is tone def to the user base and it seems the Atlassian Team is ignoring the comments. Would love to see a reply here by them to at least acknowledge their mistake and offer to re-introduce this functionality.
So much for Design Thinking or understanding your customer. Those who are replying are likely responsible for thousands of subscription seats. Ignore at your own risk.
I represent about 7500 licenses in a Fortune 150 company. It has been a fight to get Atlassian tools adopted, this doesn't make my job any easier.
36 comments