Additional use case for multiple fieldsets

[tdorsey]

Server (please complete the following information):
N/A
Is your feature request related to a problem? Please describe.
Follow on to #5083 I'd like to store a large number of custom fields in fieldsets. Consider the following simple scenario: An asset can have measurements (eg, a length) and testing information (performed by $user). Currently, this would be two custom fields, and works fine.

However, in practice, we'd like to store many more fields for both measurement and testing. Some assets (laptops) need pre deployment testing, some need measuring (server racks), and some need both (servers, hvac).

Describe the solution you'd like

Create a Measurements fieldset (Containing length, width, height, etc)
Create a Testing fieldset (Name, date of test, etc)

Assign server asset model both the measurements and testing fieldsets.
When an hvac model is added, it can then be marked both measurable and testable

Describe alternatives you've considered
This can be done currently, but many fields (10+) must be added to each new fieldset individually, which is tedious and error prone.
It also results in needing to make changes to many fieldsets whenever new information is recorded (if we were to begin tracking test duration as well as test date, it'd be nice to make that change only to the testing fieldset instead of to each new asset that needs a test duration field

#3435 might also work for us if a fieldset could be assigned to an asset category

[stale]

Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Don't take it personally, we just need to keep a handle on things. Thank you for your contributions!