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
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Published May 30, 2018 in Marketplace Apps

Three tips for boosting your board's efficiency with Story Maps

Trello is one of the most effective tools for driving your sprints. It's customizable for every Agile team and product owners and Scrum masters (SM) love it. However, Agile teams often struggle with:...

855 views 2 9
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