Performing bulk change for Edit Issues: Edit field values of issues all fields are shown by default

Issue Summary

This is reproducible on Data Center: yes

Steps to Reproduce

1. Spin up a new Jira instance and create a Sample Data Project. To get the Default Field Configuration created
2. Edit the Default Field Configuration and hide all possible fields so that you can easily see the behavior
3. Go to advanced search an do a simple JQL: project = SCRUM , then click on Tools bulk change on all Issues > Edit Issues: Edit field values of issues. Check how it looks like
4. Create a new custom field: single line tex "TEXT_CF"
5. Repeat Step 3, and see the difference. The new custom field "TEXT_CF" is there

Expected Results

Request: When creating new custom field, we should be able to decide to which field configurations it should be added. Also Jira should allow to hide more than one custom field at once.
Reason: Whenever you perform a bulk change for Edit Issues: Edit field values of issues, all fields that are not explicitly hidden, are always displayed and this could lead to confusion for Jira users. Also, having multiple field configurations, hiding the fields is a time-consuming task.

Actual Results

• New custom fields are being added to existing field configurations and by default they are visible

Workaround

There is a workaround how to bulk hide multiple custom fields, however it is not applicable for newly created custom fields: https://confluence.atlassian.com/jirakb/how-to-bulk-hide-multiple-custom-fields-in-a-field-configuration-1062244351.html