Do you have UIMaxVersions set to more than 20?

https://world.episerver.com/documentation/class-library/?documentId=cms/9/9EF43615

UIMaxVersions will affect all content types, including other CMS content and Catalog content. Setting UIMaxVersions to more than 20 can have consequences (performance, for example)

In this case I agree that there should be an individual setting for project (not saying we are going to do it :) )

Johan Kronberg: That's a great idea, but for my large scale website which has thousands of pages changing this feature could increase website load time and use up valuable server space.

Here is an example of what I'm doing: Website A - The backbone of the site structure is published. Migrating Website B & C into EPiServer and each site is in a project. This gave me the flexibility to have each website launch into the new EPiServer site (Website A) independently and in any order - so maybe website C in Project C is published first. Projects gives me the ability to publish all 200 (or more) pages of Website C all at once, all on the same day with little effort.

Now let's say Website B was added to EPiServer first and we still havne't published the project it lives in. Stakeholders would like to continue to edit and review pages but I've maxed out my 20 revisions on some of the pages associated with website B. The only current solution is to publish the page and make edits as if it's part of website A. That's not something my key stakeholders want, but its currently my only solution.

Of course it depends on the solution but you can raise that setting value to more than 20 without much effect on performance. If I recall correctly the defaultvalue way back was "unlimited".

I agree a more fine grained split of this setting is a great feature request!