Script Runner addon causing issues not to reindex

Steven Lam

Hello,

I have been having issues with the script runner for a couple months now. I am adding a post-function script to a workflow transition and when progressing this workflow transition the issue will jump to the next status, however, filters, subscriptions and queries that display this issue will continue to show the old status.

Things to note:

- I am using this script runner on completely custom workflows

- This problem is NOT happening on every workflow transition that executes the script runner

- I have tried moving the order of this execution of the post script to AFTER the issue is reindexed with the database, however, that has proved to be unsuccessful.

- Atlassian support has recommended disabling this addon which seemed to solve the issue

- The script being run is a simple commenter that adds a comment on behalf of the user. The code was actually taken from a sample provided in Script Runner documentation pages.

Any help would be appreciated.

Regards,

Steven

Vincent Thoulé

Hi Steven,

If you are using JIRA 5.1 to 5.2.9, it is possible that you are experiencing a side effect of the new way that IndexManager works. For these versions, Issues are no more indexed by the Index Post-Function, but at the end of the transaction initiated for the Workflow transition.

It means that your scripts are executed with an issue not yet indexed; or changes done by these script are indexed (if indexation initiated in the script) before the indexation initiated by the Index Post-Function.

The issue is already known : JRA-31775.

It may cause error with Script Runner, but also with Auto-Transition.

See details and workaround here.

Vincent