how to make a custom field mandatory based on value of another custom field on Jira cloud

[Test Account]

I have one custom field customfield_10046, which has two options Yes & No, if selected Yes, only then the other field customfield_10047 should be mandatory, if selected No, it can be Optional.

How to achieve this on Jira cloud? I have seen many answers in this forum using Script Runner, but nothing works out. Kindly help me out

[John Funk · Accepted solution]

Hi Sangeetha,

The ScriptRunner Behaviours tool that can accomplish this is only available on the Jira Server version. There is currently no way to do this in the Cloud. 

[Kate Kabir · Accepted solution]

HI @Test Account 

Thank you for the question. 

I can confirm that the ScriptRunner for JIRA Cloud plugin is unable to make a custom field mandatory based on the value of another custom field as the server version can with the Behaviors feature.

Also, I can confirm that the plugin cannot dynamically populate field values like it can in the server version can with the Behaviors feature. We do not have an alternative way to configure this in the cloud.

The reason we are unable to provide this functionality is due to the restricted functionality and API's which Atlassian provide inside JIRA Cloud, due to the fact that Atlassian only provides a Rest API in Jira Cloud and not the same Java API that the server version contains.

However, You may vote for a Feature Request on this at, https://scriptrunner-for-jira-cloud.nolt.io/4  if you are interested.

Thank you. 

Kind Regards

Kate

[Albert Diaz]

Hi @Kate Kabir, has this changed at all?

[Trudy Claspill]

@Albert Diaz 

The Behaviours app was released at the end of 2022 and has had several subsequent updates to enhance functionality.

You can review the documentation here.

While the documentation does indicate it can be used to make a field mandatory, I have not read far enough nor experimented with it to determine if that can be done based on the value of another field.

[Albert Diaz]

@Trudy Claspill

Thanks for the info! So apparently the Behavioral scrips do function in the cloud for Jira Software. They do not, however, function on Jira Work Management or Service Management... according to Adaptavists' documentation.

Wish I would've read that sooner before I spent a few hours trying to figure out why my script which was perfectly fine wasn't working on my Service project hahaha

[Trudy Claspill]

Do you have Scriptrunner installed on your instance?

Which posts have you tried to follow?

[Test Account]

https://community.atlassian.com/t5/Jira-questions/Can-we-set-a-custom-field-as-mandatory-based-on-other-custom/qaq-p/259960

https://community.atlassian.com/t5/Adaptavist-questions/Custom-field-condition-with-Scriptrunner-cloud/qaq-p/1060045

https://community.atlassian.com/t5/Jira-questions/How-to-make-a-Field-Required-Based-Off-Value-of-Another-Field/qaq-p/808196

https://community.atlassian.com/t5/Marketplace-Apps-Integrations/Custom-field-mandatory-based-on-another-field-on-create-issue/qaq-p/396419

Tried all the above posts. Yes, Scriptrunner is already installed

[khalid]

hi, if your project type is "service"

then this will help you

go to your project-project setting and choose dynamic forms

then you can choose for example the cascading field and the mandatory field "required".

[Jarosław Solecki _Deviniti_]

@khalid @Test Account 
Since the original post, there were some changes in Jira API and our team created a Cloud version of Dynamic Forms for Jira which resolves the problem with conditional setting the field as required based on the value of other fields. It comes with a few additional features like Set Value, Default Value for native fields and Fields Visibility. It works for company-managed Software projects right now.