In this period of Smart Working I am deepening my study of Atlassian products, in particular Jira Software and Jira Service Desk.
One of the things that impressed me most about Atlassian products is the flexibility of the search engine given by the JQL (Jira Query Language).
I must say that initially when I saw the first examples of JQL I looked at it with suspicion. I’m used to querying MySQL to find the data I need, and a higher level language didn’t seem like it would be that flexible to me.
I was wrong, because I had the mindset of the system administrator who has access to the entire database and looks for practically all the data entered into the system, while often the person who accesses the data is an operator or a supervisor.
And I was also wrong because I had not yet seen all the JQL Operators and the many functions that you can use.
To give you some examples, thanks to the operators WAS, WAS IN, WAS NOT, WAS NOT IN, and CHANGED, it’s possible to go back to the list of open tickets in a range of dates which a normal “agent side” search doesn’t really show.
Here’s an example of a JQL statement:
status WAS "Open" AND (created >= <start date> and created <= <end date>)
Also thanks to JQL Functions you can have the list of tickets created or modified since the last time the operator logged on.
Here are two examples of beautiful JQL functions:
created >= lastLogin() OR updated >= lastLogin()
updated > lastlogin() AND assignee = currentUser()
The possibilities are many. In addition, the filters can be shared with other agents and can be used to feed dashboards and graph results.
On the internet you can find many examples and tutorials on the use of JQL, certainly a theme to be explored further!