Add the ability to make Attachment field as Required through Field configuration, not just workflow validator

Update 1 February 2024

Adding screenshots to further illustrate the request. Currently, Attachments can be made required using a Use workflow validators for company-managed projects. It is not possible to make the Attachments field required using a field configuration. Related feature request: JRACLOUD-76479 – Make workflow validator required fields more visible on screens

Current behaviour

Before clicking Create with no attachment:

After clicking Create with no attachment:

Desired behaviour

Allow Attachment to be required in field configurations so it can behave the same way as the Summary field in the above screenshots - the field is individually highlighted with asterisk and red highlight, and its required status is highlighted before transition.

Original description

Currently, it's not possible to make the attachment field as required though Field configuration. Its only possible to make it required through Workflow validators.
However , due to this feature request https://jira.atlassian.com/browse/JRACLOUD-30636 ( which is closed as Wont do) , currently fields marked as required in "Validators" do not show the red asterisk sign.
Users are shown the error message only after filling all the details.
Please consider making Attachment field as required from Field configuration.