Form versioning

[extensibleseth]

The problem (description, use case, screenshots...)

Fields were removed from a form which now needs to have them again.

The solution (that feature you'd like to see)

Provide optional versioning for form configurations, either separately or as a whole. Rules, notifications, redirect, title, etc...
Also allow users the option to retain data on field removal, and remove it afterwards while retaining the removed field configuration. Extra fancy would be the option to merge like fields to allow for recreated fields to become the restored field without loss of submission data.

Alternatives you've considered

[BenParizek]

Thanks @extensibleseth. I'll tag this as a FR and consider our options when I have a chance to dig deeper and explore if Craft versioning may be able an option for custom elements like Forms.

Right now, when deleting a field it does prompt the user to indicate that the field and its data will be removed. That would be the time to grab a report for the archives. But I understand that's not what you are asking for here.