nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to set field is required based on other field value in drop down option

Velkuri Balaji

Hello,

We would like to set "Preliminary Estimate" field is required when we select "Epic Type" field as 'Production Work' (in drop down options).

To achieve this we are trying to use behaviour function but I don't have much knowledge on Script, Could anyone help and provide the right script to setup this feature.

Note: " We are using Jira Cloud not Jira Server, Behaviour feature is now available for Jira cloud "

Thank you

Balaji

Accepted answers

All comments

Evgenii

Hi, @Velkuri Balaji

Try this:


const preliminaryEstimateField = getFieldById("customfield_12345");
const epicTypeField = getFieldById("customfield_54321");

if (epicTypeField.getValue().name == "Production Work") {
    preliminaryEstimateField.setRequired(true);
};

More information on behaviours can be found here:

https://docs.adaptavist.com/sr4jc/latest/features/behaviours

and here:

https://www.youtube.com/playlist?list=PLnsCytbU4bI6SwVAp1DJlzua9vk1oLQ-G

Velkuri Balaji

Hi @Evgenii

Thank you for your quick reply, It is working on issue creation level, If we select Epic Type as 'Production Work' it is asking to fill 'Preliminary Estimate' field and if we select Epic type as ' Testing' then 'Preliminary Estimate' Field is not required to fill which looks good.

However, After create an issue by selecting Epic Type as 'Testing' in edit screen users are able to change Epic type field as 'Production Work' here it's not showing required to fill 'Preliminary Estimate' field

Example :

While creating issue users can select Epic type as 'Testing' and after that they will open issue and change the Epic Type as ' Production Work' and here they are Skipping the Preliminary Estimate Field.

Could you please suggest how to achieve it.

Thank you

Evgenii

Ok, you have to make behaviour that looks for field changes on issue creation and on changes in issue. Add to behaviour field "Epic Type" and in script section in use something like this:

const changedField = getChangeField();
const preliminaryEstimateField = getFieldById("customfield_12345");

if (changedField.getName() == "Epic Type") {
if (changedField.getValue().name == "Production Work") {
        preliminaryEstimateField.setRequired(true)
    }
}

Here is example, how it can be made:
https://youtu.be/T_22rKXWNrg?list=PLnsCytbU4bI6SwVAp1DJlzua9vk1oLQ-G

Not sure, that it will help, haven't found exact example. But in server Jira it works nearly that way.

Velkuri Balaji

Hi @Evgenii

Thank you for your time and efforts,

I have tried above script to affected field as Epic Type but still it doesn't work on the edit screen level. Could you please correct me if I'm doing somewhere wrong

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

adaptavist

jira-cloud

behaviours