Need help understanding the reason behind JQL syntax

Mark Hansens_34vza2

Can someone please help me understand the reasoning for the apparently inconsistent syntax with JQL functions?  Some support '=' but not 'in', others are the opposite, for example.  I am trying to study for the Jira Cloud Admin cert and I just can't make sense of this and there is too much for me to commit to just strict rote memory.  If I can understand the reasoning, then it might help me to understand and reason through the answers.  Help?

Walter Buggenhout

Hi @Mark Hansens and welcome to the Community!

I did not develop JQL and it goes back more than 20 years, so it won't be easy to try and share "the" reasoning behind JQL.

A couple of things might help, such as:

• text fields (like summary or description) don't support '=' search. You will mainly see '~' as an operator in those cases.
• 'IN' is used if you want to combine multiple options in a list. It can work as an alternative to 'OR' and as such it allows you to write Project in (ProjectA, ProjectB, ProjectC), which is significantly shorter and easier than "Project = ProjectA OR Project = ProjectB OR Project = ProjectC" although both will give you the same results.
• It looks as if option fields can only be searched with (NOT) IN, which probably is to cater for scenarios where you can select multiple options. Cascading select and checkbox fields e.g. are such fields.
• Sprint functions like openSprints(), futureSprints(), closedSprints() by default assume that multiple options are returned.
• The SLA example completed() only allows you to select '=' or '!=' simply because this only can be one of the two options: the SLA cycle is completed or it is not. There are no other options there.

As a recommendation, just try to think about what these functions are designed to do. Once you're there, the operators tend to make sense.

Hope this helps!