Team → a person → Automatically add to new projects puts that person on every project as it is created. It was working for projects made in the app, duplicated from an existing one, or created through the API — but not for projects brought in by a CSV import, which is the one route by which a workspace creates a lot of projects at once. Anyone relying on the setting had to go back and add themselves by hand to exactly the batch where it would have saved the most work.
Importing now assigns them, in the same transaction as the import itself, so a part-finished import cannot leave some projects assigned and others not.
Importing from Harvest deliberately still does not do this. That import brings across Harvest's own record of who is on which project, and adding people on top of it would put them on projects Harvest says they are not on. The setting itself comes across from Harvest, so somebody who had "access to all future projects" there keeps it here.