This issue has to do with the data type of a Yes/No field and the value that is stored on the edit query page.
When stored the value is either the string "True/False". However when creating the custom field you can pick the data type (which you should not be able to do) as this causes an issue with running the query. See the sample query "Test Query (Administrator)" in the first project. The value of the query is "0" and it throws an error on execute.
Ideally if a Yes/No field is picked the data type would be "string" and the checkbox rendered would store "Yes" for true and "No" for false in the issue field. Also when the field is rendered in the query page rather than having the textbox field show up a dropdown with "Yes / No" as the field value to pick from would be displayed.
This way when a saved query that has a custom yes/no field runs the values used would match.
Something along those lines.
When stored the value is either the string "True/False". However when creating the custom field you can pick the data type (which you should not be able to do) as this causes an issue with running the query. See the sample query "Test Query (Administrator)" in the first project. The value of the query is "0" and it throws an error on execute.
Ideally if a Yes/No field is picked the data type would be "string" and the checkbox rendered would store "Yes" for true and "No" for false in the issue field. Also when the field is rendered in the query page rather than having the textbox field show up a dropdown with "Yes / No" as the field value to pick from would be displayed.
This way when a saved query that has a custom yes/no field runs the values used would match.
Something along those lines.