Zero as default value in Spinner is interpreted as an empty field when the email template is modified

Hi. I have reported this is issue over a month ago now but it hasn't been fixed so I am assuming it is low priority. Also for clarity's sake I am re-posting it here:

 

BUG: removing a row from the email template makes the template mistakenly interpret the default value 0 in the spinner as an empty field so it isn't reported in email output. 

 

To replicate the unsolved problem in my form, I created a new form with just two elements:

1) a text question 

2) a spinner 

 

 

This is original template: 

 

Then I removed the text field row {textQuestion}. This is how template looks:

 

 

 

 

In my experiment there are 3 scenarios: 

 

 

Scenario 1: If the original email template is kept untouched, the default 0 result is reported correctly in the email

 

 

 

 

Scenario 2: If I delete the text question row {textQuestion} in the email template, AND if the spinner  value is left at default value = 0 (which is a valid number, NOT an empty field), the result disappears from the email. This is a BUG. 

 

 

 

Scenario 3: With the  text question row {textQuestion} deleted, if I chose a different value than 0 in the spinner (i.e. 1), then the spinner result is reported correctly in email.   

 

 

 

 

 

So this is the error: removing a row from the email template makes the template mistakenly interpret the default value 0 in the spinner as an empty field and it isn't reported in email output. 

 

I am urgently waiting for a solution to this BUG. 

(I am longtime paying customer of Jotform. I use this form with my clients, and I might have to switch to another form builder if this doesn't get solved as I need to have the form working without errors. I hope you understand.)

Thanks for your timely help! 

Yes, there is no update yet with your original ticket here https://www.jotform.com/answers/2134764. I'll send a follow up to the assigned team. Unfortunately, this is the only thing we can do for tickets. Once we have an update, you will be notified there.

Can you not use the Short Text Entry field? I've tested this field, and it worked. 

Hi. I have not seen any update on this bug after 6 months so I have decided to downgrade to free account. 

Greetings.

We are sorry to hear that you were forced to downgrade your subscription.

I will send a message to our Developers to see if there are any updates related to this problem. As soon as we hear back from them, we will let you know in the original ticket. 

We apologize for the inconvenience.