Database Customfields and {customfield_nnnnn} references in the SQL

I am using the same Jira screen for creation and update and have four cascading database customfield select fields (with 4 child fields).

On the 2nd, 3rd and 4th SQL calls I'm using {customfield_nnnnn} values in the SQL from the current issue. The problem is that in the CREATE context one or more of the customfields don't exist and but any reference to them in the SQL causes an uncatchable error.  

I can branch the SQL to deal with the two contexts (either create or update), but I can't handle the handle the SQL error where the field does not yet exist.

Is there anyway I can treat a non existent cf field as null in the SQL? 

0 answers

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 29, 2018 in Marketplace Apps

How to set up an incident workflow from the VP of Engineering at Sentry

Hey Atlassian community, I help lead engineering at Sentry, an open-source error-tracking and monitoring tool that integrates with Jira. We started using Jira Software Cloud internally last year, a...

1,378 views 0 8
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