Full Question:
- When bulk importing pages into Confluence using the "Import Word Document" feature, Is possible to assign a specific "Blueprint" to those pages during that process or can a user retroactively add blueprints after bulk page creation is complete?
Goals:
- Generate 3 levels of pages and sub-pages inside a space using "Import Word Document".
- Basic Example:
- Root Page #1
- Sub-Page #2a
- Sub-Page #2b
- Sub-Page #2c
- This can easily be accomplished by using the "Import Word Document" feature. It will generate and split the pages by using Word's H1, H2, and H3 headers when organizing a page tree. Next, change the "Split by header" dropdown during the import process to your current page tree level you are generating.
- During the setup of the of the "Import Word Document" or altering the word document itself, I would like to be able to assign a specific "Blueprint Template" to those pages during the creation or retroactively assign the "Blueprint Template" after the pages have been generated.
Note:
- I'm not sure what has been updated, but after I figured out how to generate tree pages, I thought I could copy/paste the template from another page into those new pages manually. During my attempt to copy/paste templates manually there is some difference between my old space/page and my new space I am trying to restructure. Confluence won't allow me to copy "Page Layouts" formatting into my new page.
- I created a mock up template inside my new space > page and tried copying that into another page and I wasn't able to even copy all. I was only able to copy a specific Page Layout cell.
- If anyone has any suggestions, guidance, or a better approach on how to accomplish bulk creation of pages + bulk assigning a blueprint template to those pages, I would be very grateful for any help. I may not not be utilizing another feature in Confluence that might accomplish this goal, so please let me know if I'm missing something. Thank you in advanced.
Edit:
After digging a little further, the copy/paste issue is due to the update with the legacy editor and new editor in the same space.
- Potential Solution from Atlassian?