The issueFunction JQL search is not working in Jira Cloud board

[Edoardo Lucat]

Since we migrated to Jira Cloud it is not possible anymore to configure the Agile Board swimlanes with a JQL query containing the issuefunction.

In the “old” Jira I used to configure the swimlanes as you can see in the attachment, using the following JQL queries:

• type = Story or issueFunction in subtasksOf("type = Story")

• type = Task or issueFunction in subtasksOf("type = Task")

• type = Bug or issueFunction in subtasksOf("type = Bug")

Now if I try to use the same I receive the following message: Field 'issueFunction' does not exist or you do not have permission to view it. Update the query and save it again.

I need to find a solution to group Stories and their sub-tasks, Tasks and their sub-tasks, Bugs and their sub-tasks together in the swimlanes of the board.

[Trudy Claspill · Accepted solution]

Hello @Edoardo Lucat 

Welcome to the Atlassian community.

issueFunction is a JQL capability added by a third party app, like ScriptRunner.

Due to architectural differences in Cloud it can't be used directly in native JQL entry fields. Instead the filter has to be created and saved through the screen provided by the third party app. Then in the native JQL fields you would reference the filter by name:

filter = "Name of the Filter"

For ScriptRunner the screen for creating filters is named Enhanced Search, and is found under the Apps menu.

The app vendors describe this limitations in their app documentation.

[Edoardo Lucat]

I already tried it but it seems not to work (probably it's me not being able to do it).

I tried to insert a query but it always takes too much time and times out making impossible to save the filter.

I have no clue how to solve this

[Trudy Claspill]

Can you provide screen images to illustrate:

• "but it seems not to work"
• "it always takes too much time and times out"

For the second one, I suspect that you may be trying to create the Enhanced Search query exactly the same as the Swimlane queries you showed:

type=Story or issueFunction in subtasksOf("type=Story")

When you try that from the Enhanced Search screen it has no idea about the filter that already exists to select issues overall for your board. So in Enhanced Search it is trying to execute that filter for all Story issues in all projects in your instance.

You need to refine the filter in Enhanced Search to encompass some of the criteria used by your board's filter, to reduce the results set that Enhanced search is trying to get.

If you board is for a specific project, add the project criteria to the filter

project = X and (type=Story or issueFunction in subtasksOf("project=X and type=Story")

[Edoardo Lucat]

I already tried specifying the project and it didn't work,

project = X and (type=Story or issueFunction in subtasksOf("type=Story")

but now I tried with the same query you reported here above and it worked!

project = X and (type=Story or issueFunction in subtasksOf("project=X and type=Story")