Customfield inserts in database.

[Daniel Micallef]

When an issue is created and a customfield is not set in JIRA, no inserts are made into the mysql database. Therefore the following condition in the workflow will not be satisfied, and the JIRA issue not able to be closed.

if customfield is null

Is this the way JIRA should function? And if so, is there a way in which I am able to make an insert with a value of NULL for the empty (unset) customfield?

[Sten Sundelin]

FYI - JIRA Workflow Toolbox (paid for add-on) has a validator to check if a custom field has been initialized (not null).

[Nic Brough -Adaptavist-]

Yes, it deliberately puts nothing in the database when a custom field is left empty.

It should be irrelevant to you though, as the UI, REST and internal code all recognise and handle that as "no value set".

The way you have phrased this suggests you might be trying to insert data with SQL.  NEVER do that with a JIRA database.

[Daniel Micallef]

Hi Nic, thanks for your answer. No I am not trying to insert any data via SQL. On the other hand, in the JIRA workflow, I have set a condition, which enables an issue to be closed if and only if the value is not set (i.e. is NULL). Naturally if nothing is inserted into the database the customfield value  does not exist (and therefore is not NULL), hence users are unable to close an issue. Could you suggest a workaround for this problem?

[Nic Brough -Adaptavist-]

There's no problem there, and you're over-thinking something.  The API knows that a custom field is empty and you use that in your condition.

Could you show us what you've got for your condition?