The execution information for script listeners loads slowly when many are setup. You end up having to wait a long time for the execution information to populate.
I reproduced this by setting up 100 script listeners which are all triggered on the same event.
The cause of this is that there are many calls to the diagnostics endpoint, for example: <base-url>/rest/scriptrunner/latest/diagnostics/results?functionId=122e75d0edb0786b596a65b681e88b28107311d2&_=1483367008482 to retrieve the execution information.
This is also an issue in other places where we have diagnostics information, for example script post-functions. Although it is unlikely there will be hundreds on one transition.
There are two options I see to solve this problem:
- Have a bulk diagnostics endpoint which can retrieve the execution information for batches of listeners (limit number of calls to the server)
- Paginate the list of listeners to read a particular number at a time and you click a button to load another page