Issue with JQL Query filter KANBANBOARD

[Tiago Pereira]

A fellow colleague from my company complained that since the migration to cloud the KANBANBOARD related to his project stopped working, when trying to use already existent JQL filter (project =PDP and issuetype"Epic Link" = PDP-715 AND issueFunction not in hasSubtasks() OR project = PDP AND issueFunction in subtasksOf("'Epic Link' = 'PDP-715'")  I get this error message "Error in the JQL Query: Expecting operator but got 'Epic Link'. The valid operators are '=', '!=', '<', '>', '<=', '>=', '~', '!~', 'IN', 'NOT IN', 'IS' and 'IS NOT'. (line 1, character 27).

I can't also switch to basic filter, could you please support w/ this?

[Alex Koxaras -Relational-]

Hi @Tiago Pereira and welcome to the community,

The message is correct, and your JQL has a minor error after "issuetype". You write

......issuetype"Epic Link" = ...

Which doesn't make any sense.

Your JQL, in case you want to use issue type should be something like:

(project =PDP and issuetype = "Task" AND "Epic Link" = PDP-715 AND issueFunction not in hasSubtasks() OR project = PDP AND issueFunction in subtasksOf("'Epic Link' = 'PDP-715'") 

[Alex Koxaras -Relational-]

@Tiago Pereira to reply to your answer:

But the "issueFunction" seems to not be present on the Syntax list.

The error produced on your post, clearly states a problem with "Epic Link", due to the missing AND/OR operator. This is one problem.

If you encounter a problem with issueFunction, is due to the fact that scriptrunner in cloud (and JQL) doesn't work like on the server. Scriptrunner cloud provide a different "search page", called enhanced search:

[Alex Koxaras -Relational-]

@Tiago Pereira to reply:

Hi Alex issue w/ Epic link is gone but now when trying to search w/ full JQL I get an parsing time out error, not sure how to solve this.

Also used the issue function option you showed seems to be correct I believe

ON your JQL use parenthesis to narrow down your results. In addition consider if you actually need the below statement, as it will return all subtasks: 

issueFunction in subtaskOf("")

And one more advise would be to start adding jql statements bit-by-bit and see what is causing the problem. 

[Alex Koxaras -Relational-]

@Tiago Pereira first of all, it would be great if you could reply beneath my reply, on this post of mine :)

Second of all, id depends what issues would want to yield. What is the requirement of the JQL? What issues are you trying to find?

[Tiago Pereira]

But the "issueFunction" seems to not be present on the Syntax list.

[Tiago Pereira]

Hi Alex issue w/ Epic link is gone but now when trying to search w/ full JQL I get an parsing time out error, not sure how to solve this.

Also used the issue function option you showed seems to be correct I believe. 

[Tiago Pereira]

How about the  "hasSubtasks()" is it the same as the option we have on the issue function?