This question is in reference to Atlassian Documentation: Page History and Page Comparison Views
We have a few habitual savers and more than a few documents that are being constantly updated. While we can work on the staff to break them of their urge to click save, we would like to know if there is an upper limit to the number of page revisions a single page can have in history. Thanks!
There is no limit to the number of versions you can save. I haven't checked if there is technical issue once you reach a certain number but that would be quite an accomplishment if you can hit that mark
To Jobin's point, we have had some attachments with over 1000 revisions. No problem. However, it may begin - depending upon attachment size - to start taking up server space, so keep that in mind in case that could be an issue for you. We just go in on those known pages and delete the many-times-updated attachments from time to time and then upload the latest version to begin the versioning process again.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
+1 for Jobin and Tom. Also, you should encourage your users to save regularly, because the consequences of NOT saving regularly can be significant. It depends on how regularly you've set Confluence to save drafts, but if you've got 120 users and they all lose 5 minutes work, that's 10 man-hours down the drain.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you everyone for your responses. I admit to being gun shy about software limitations I've run into in the past. Data corruption is not fun and we've hit some weird limitations over the years for having too many records.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.