Steps to reproduce:

1. Create a multi-repository setup with default and second repository:

   ezplatform:
       repositories:
           default:
               fields_groups:
                   list: [ content, test, metadata ]
                   default: content
   
               storage: ~
               search:
                   engine: '%search_engine%'
                   connection: default
           second:
               fields_groups:
                   list: [ content, features, metadata ]
                   default: content
               storage:
                   engine: legacy
                   connection: second
                   config: {}
               search:
                   engine: '%search_engine%'
                   connection: second
   

           admin2:
               repository: second
               cache_service_name: 'cache.tagaware.filesystem2'
   

       siteaccess:
           list: [site, test_en, test_ger, admin2]
           groups:
               test_group:
                   - test_en
                   - test_ger
               site_group: [site]
               admin_group: [admin, admin2]
           default_siteaccess: site
   

2. Update Article Content Type on two Admin site accesses (admin and admin2).
3. Edit name fieldtype and check for field groups.

Result:
One can see content, test, metadata groups on both site accesses.

Expected result:
One can see content, features, metadata groups on admin2 site access.

Note:
Field groups defined for another repository are not taken into consideration. When having field_groups set on second repository, both site accesses have default configuration.