Issue Summary

Currently, Jira Cloud Bulk Edit determines field editability based solely on project permissions and by current design, it works independently from respect to the Edit Screen configuration.

Due to this design, fields that have been intentionally removed from the Edit screen can still be modified through the Bulk Edit operation if the user has the required project permission.

This creates an inconsistency between single-issue editing and bulk editing, making it difficult for administrators to enforce editing restrictions using screen configurations. The enhancement request is to provide an option, ie for Bulk Edit to honor the Edit Screen configuration or Not for end users. 

Current Behavior: 

1. Configure the project's Edit Screen and remove a field. 
2. Ensure the field is still available on the Create and/or View screens.
3. Grant a user the required project permission to edit issues.
4. Go to the Jira Search and Search for multiple issues using filters or JQL
5. Select Bulk Change option
6. Observe the list of editable fields.

Bulk Edit ignores the Edit Screen configuration and determines field availability solely based on project permissions. As a result, fields removed from the Edit Screen are still available for editing during Bulk Edit if the user has the corresponding project permission.

Post enhancement Expecations: 

Provide an option for admins to decide if Bulk Edit and screen configuration should work together or not. This option can expand to include a work type level control as well so that in different work types, admins can setup configurations to be able to restrict bulk edit from making changes that are blocked by restrictions at a screen level.