How to make attachment mandatory on Jira Cloud

[ivan.lose]

As of this moment I've been trying to get attachment to become mandatory for an specific set of screens, but, this is not possible as of now. Is there a way using scriptrunner like on Jira Server? Or is this another feature not available for Jira Cloud?

[Nic Brough -Adaptavist- · Accepted solution]

Attachments are not a field, and hence don't show up in field configs for you to make mandatory.

Scriptrunner is available for Cloud, but it is a very different beastie (it was rewritten from scratch for Cloud, and the Cloud app framework is completely different).

Cloud does not provide us with a way to do mandatory attachments on the front end (yet), the best SR can do is a validator (so you can stop people progressing issues through the workflow if they are missing attachments).  For the specific cloud script for that, see https://docs.adaptavist.com/sr4jc/latest/features/workflow-extensions/validators/example-validators

[Maura Swart]

If you go to Project Settings > Request Types, and view the Request form Visible fields, you can define the Attachments field as required.

[ivan.lose]

That works for Service Desk projects, but not software projects.
This is quite useful nonetheless, so thanks for the answer!

[Maura Swart]

I'm glad the answer was helpful. I thought your question was about a Service Desk project since this thread is under the Jira Service Management product in the Community. You may want to post the same question under Jira Software.

[Jose Luis Gaitan]

Hello, @ivan.lose ;

Being a Jira Administrator, into the Administration menu, in the field configuration you can make a field required.

I enclose a link with onformation about field configuration:

https://support.atlassian.com/jira-cloud-administration/docs/specify-field-behavior/

[ivan.lose]

Hello @Jose Luis Gaitan 

As a matter of fact, attachment doesn't have this option. As would happen with Summary (which is required by default). Not sure which sort of configuration they are under, but they are above any custom field configuration I have at hand.