Requiring Values for Field

Hello, I am trying to force users to fill in values for a custom field if the value of a different field is set to a certain value.

Example: I have a custom field "Linked Issues". I want users to have to provide a value for this field if they specify the value "Duplicate" in the Resolutions field.

1 answer

1 accepted

I guess you want to perform this validation when performing a certain workflow transition. You can write a Groovy script validator for this. You need to install Groovy runner plugin for this.

Using Groovy, you can check the values of Resolution and custom field, and then display an error message and prevent status transition.

Alternatively, you can use use Behaviours and Groovy runner plugins together. Behaviours may work in issue edit screen as well. I guess following code will work for Behaviours.

if(!getFieldById("customfield_10000").getValue() && getResolutionObject().getName() == "Duplicate"){
  getFieldById("customfield_10000").setError("Resolution is Duplicate. You must set a value for this field.");
 } else {

By that you mean the list of issue links?

So, as per my understanding, if the Resolution is Duplicate, then at least one issue link (probably the duplicated issue) must exist. Am I right?

I made a mistake, Linked Issues is not a custom field, it is a field provided standard with Jira. I can't get it to work, because I am not sure how to specify it to throw the error if Linked Issues is left blank.

That is correct. I am trying to force our users to provide at least one issue link.

You have to have Groovy runner plugin for this.

For the workflow status transition where you need to perform the validation, add a 'script validator' - 'Simple Scripted Validator'. Part of what you need is already there - a bultin line of code. (Has at least one outward duplicate link)


If you can change it to something like this, it should work.

issueLinkManager.getOutwardLinks(issue.getId())*'Duplicate') || issue.getResolutionObject().getName() != 'Duplicate'

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,667 views 18 21
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you