JIRA & ScriptRunner & (issueFunction in subtasksOf)

[Olga N]

Hello!

We are using the Cloud version of JIRA. We'd like to search all sub-tasks of stories that have a special label or a special field (for instance, all stories with labels=backend).

We've created a filter with Script Runner based on a query with "issueFunction in subtasksOf". But the filter changes automatically if we use it for creating a Board (Kanban or Scrum). The function "issueFunction" changes to "real numbers of stories which have sub-tasks". It's fine, we're not worrying how it looks but it never changes if we add new stories.

[Kristian Walker _Adaptavist_ · Accepted solution]

Hi Olga,

Thank you for your question.

I can confirm that the way that the filter synchronisation works is buy when you save a filter inside of the enhanced search page that it creates a copy of the filter as a standard Jira filter and after the synchronisation period specified in the Filter sync interval period parameter on the settings page as described here. 

It then it updates the standard Jira filter to contain a list of issue keys for the issues returned by the enhanced search query.

This means that after the filter synchronisation period you will need see the new issues appear when you refresh the page in your web browser.

I hope this information helps

Regards,

Kristian

[Olga N]

Thanks a lot for your answer! It's working now!

Will the FIlter of the Kanban board have 1000s of Story numbers in the future or stories will disappear after their completion?

[Kristian Walker _Adaptavist_]

Hi Olga,

You are welcome.

Stories will continue to show unless your JQL has a condition in it to not show issues in the complete status e.g Done or Closed.

I hope this information helps.

Regards,

Kristian

[Olga N]

Yes, Thanks!