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
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Bridget Sauer
Published 10 hours ago in Marketplace Apps

Calling all developers––You're invited to Atlas Camp 2018

 Atlas Camp   is our developer event which will take place in Barcelona, Spain  from the 6th -7th of   September . This is a great opportunity to meet other developers and get n...

34 views 0 3
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