It's not the same without you
Join the community to find out what other Atlassian users are discussing, debating and creating.
I was reading this technote.
According to the note, if you make a major version upgrade (from 4.0 to 4.2 for instance), you have to save all custom layouts and reaply it, but I don't understant why you need to perform step 4 (Click Reset Default next to the layout whose customisations need to be reapplied).
After the upgrade the new version's default layouts overwrite any customisation? or
Customisations are preserved and the idea is to merge them the new defaults? Step 5 says reapply customisations, not merge.
Thanks for your help.
I recently went from 4.1.2 to 4.2.3 and did not have to perform that step. I talked to a few folks at Summit about the upgrade, and they said that if it went OK, I wouldn't have to do any merging (and I didnt).
I'm assuming Step 5 "means" merge, but I would definitely try the upgrade without blowing away your custom layouts first.
My custom layouts were maintained when I did a database dump and restore. (Note: I did not export as XML and then import into the new Confluence version.)
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.
Read moreHi Community! Kesha (kay-sha) from the Confluence marketing team here! Can you share stories with us on how your non-technical (think Marketing, Sales, HR, legal, etc.) teams are using Confluen...
Connect with like-minded Atlassian users at free events near you!
Find a groupConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.
Start an AUGYou're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.