Non-Required Field treated as Required.

When calling our JIRA createmeta service, we are noticing that certain fields are not marked as required in the json, yet when attempting to create an issue, the field is treated as required. Is this a known issue? If so, is there a workaround available?

5 answers

1 accepted

Did you try the Where is My Field feature, I know the field does display but there may be a scheme that is not 100% correct and Where is My Field might show you the problem.

As it turns out, the issue was indeed the schema. Ultimately we had to file a ticket to our JIRA admin and they responded with the below statement.

"Currently, your project is using [a specific] Schema that has some Business Rules associated with them.

The business conditions will come across and performs the validations while creating/editing issues.

One of the business rule condition is "While creating issue type "Affect version is required".

That's the reason you are getting this validation message when Affect Version field is empty.


Making this field as "Required" will be applied to all issue types, but other issue types may or may not require this field."

Thank you all for your speedy comments!

0 votes
Joseph Pitt Community Champion Nov 18, 2013

Which fields? By default the summary field is required to create an issue. I don't know if you can get around that. also, resolution is required if it appears on the screen and as such should only be displayed on the transition screen on the transitions where it should be set.

Specifically the versions field, also called Affects Version/s , in the rest json response the field is not marked as required, but when attempting to create an issue, it states that the field is required.

What happens when you create the issue in the web UI? Is the field shown as mandatory with the little red star?

No, the field is not shown as mandatory.

Ok, in that case, the field is not mandatory, so the JSON won't contain anything to say that it is.

But, the error you are seeing is down to a validator, which is a function of the workflow, and there's no way the JSON can know that you have configured it that way.

It's an unusual thing to do - use a validator on create to make things mandatory, and probably unnecessary. If you do it in standard field config instead, it'll create the correct JSON as well as make it mandatory on screen.

Perhaps there is something in the workflow transition which is requiring a value in those fields.

Looking at the other fields there is an astreik next to the field name, is there an astreik next to Affects Versions. It is hard for me to verify in your screenshot. Did you try to create the issue without an Affects Version? Maybe "Version is required." is just in the field description, because that is not the typical JIRA field required indicator.

John B could be right as well, it could be a validator in the workflow. Check out validators in this article,

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Jan 08, 2019 in Jira

How to Jira for designers

I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...

1,296 views 5 10
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