The issuefunction queries (atleast dateCompare function) runs in the background even after the user session is killed

Description

*This issue has moved*

This issue has been moved permanently to Adaptavist's Product Support JIRA instance.

All existing users of this instance should have the same username on our Product Support instance. However, you will very likely need to click on the
Can't access your account link in order to reset to a new password.

Hi,

I'm noticing that some expensive issue functions, particularly dateCompare continue to run in the background even after I kill the browser session. As I'm an admin in our system which has close to 700k issues, this is very expensive and taking 100% of the server cpu. Not sure how to kill the job as well.

Any thoughts on how to kill the job that is running without bouncing the app? Here is the query that I ran:

issuefunction in ("", "updated > resolutionDate") and project = XXX

and it looks like it searches the entire data and not just the condition, and then I tried

issuefunction in ("project =XXX", "updated > resolutionDate")

which returned results quicker.

Thanks,
~ilango

Environment

None

Activity

Show:
Jamie Echlin
October 4, 2015, 12:32 PM

There's no way of killing it, because there's no way of knowing whether the browser is closed.

You should use a filter query as the first param, this is discussed here: https://scriptrunner.adaptavist.com/latest/jira/jql-functions.html#_performance

> issuefunction in ("", "updated > resolutionDate") and project = XXX
> and it looks like it searches the entire data and not just the condition, and then I tried

Yes, it checks the condition across every issue, because there is no filter query as the first arg.

We will probably provide a way for admins to limit the number of issues that can be scanned.

Your pinned fields
Click on the next to a field label to start pinning.

Assignee

Jamie Echlin

Reporter

IlangoA

Internal Complexity

Unknown

Internal Value

Unknown