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
Except that this does not work the same way as it used to. Previously, you were able to import a Word document to replace an existing page. Replacing the existing page would then keep all document links pointing to the newly imported content, and keep all existing labels which were already attached to the page being replaced.
The new import feature simply creates a new page, with a new name, and does not appear to be able to replace an existing page.
Engaging with the announcement post (https://community.atlassian.com/t5/Confluence-articles/Announcing-changes-to-Microsoft-Word-import-in-Confluence/ba-p/2204406) may be a good option for those who still have questions. Hope that helps.
There is the problem of the new word import. It makes it impossible to import large documents, and split based on headings that maintain the link integrity of the imported object.
Is there a workaround for this? Is there a way to switch to the advanced details approach with upload choices?
And this is proof of just how out-of-touch Atlassian is. First off, this does nothing to actually address the shortcomings of the new import feature (such as there being no way to break a document in to separate files anymore). Second, this is a "shorts" video, which means there's no way to fast forward or rewind. The video goes quick, and if you missed something, you have to watch the whole thing again.
The related issue is in GATHERING INTEREST phase, people, VOTE, VOTE AND VOTE.