Hey,IQL only supports double quotes when an object or attribute contain whitespaces. This is a bit inconsistent with how many other languages do this.This becomes quite clear when using the JQL function iqlFunction.The function itself requires that the IQL is quoted (the outer quotes) and if the IQL contains objects/attributes containing whitespaces these need to be quoted as well (the inner quotes)This is a very common scenario.If I am only using double quotes I will need to escape all the inner quotes to make this work, e.g. "My Domain(s)" in iqlFunction("\"Parent OU\" IN (\"Accountable CEO\")") This is really hard to read and trying to get users to understand this is almost impossible.I played around mixing double and single quotes here since this is a common way to get around this issue when you have outer and inner quotes present and found that the iqlFunction itself is happy with either single or double quotes and if I use this approach having single quotes as my outer quote the JQL will be a lot cleaner: "My Domain(s)" in iqlFunction('"Parent OU" IN ("Accountable CEO")')_However, if I try the other way around having double quotes as my outer quotes and single quotes in my IQL query, Insight is throwing an error: *IQL in iqlFunction is not valid*The common practice in my opinion is that single and double quotes shall be possible to use independently meaning that they mean the same thing and shall be used when two sets of quotes are needed.I can refer to the similar JQL function, _issuefunction provided by the Script Runner which handles these two variants independently.Also in most programming languages it is ok to use either single or double quotes when e.g. a string is defined. It is the based on the user's preference which to use.So please consider supporting single quotes as well in IQL so that the user can choose how to manage situations when you need two sets of quotes.