Script Listener (via Scriptrunner) is showing unrelated log.warn messages in the logs

[Roy Powell]

I have a Script Listener via Scriptrunner (Jira DC) that is showing unrelated logs. Often when I look at the logs for this listener, I will see log.warns that are for a separate Scripted Field, not at all related to this listener.

Has anyone seen this occur before? Is there an issue with Scriptrunner itself, or is it with my logging practices?

[Ram Kumar Aravindakshan _Adaptavist_]

Hi @Roy Powell

Could you please share the log message that you are getting?

Also, if it is from a specific Listener code, could you also share that code so I can review it and provide some feedback?

Thank you and Kind regards,

Ram

[Roy Powell]

Unfortunately I cannot share those details here due to the nature of the client work, however I can briefly describe.

There is a scripted field for "Repo Name" that automatically pulls in repository names from Bitbucket. This field essentially looks at any associated merged pull requests for a story, and pulls repo name(s) accordingly (comma separated if multiple repos merged against). That scripted field has a few logs, stuff along the lines of:

• log.warn("Number of pull requests: ${requestArray.size}.")

In an unrelated listener, which is just analyzing fix version details on every "Update Issue" event, I'm seeing those same logs from the Repo Name in addition to all of the listener's expected logs. But this is only one example, there are other scripts that "infect" various logs across the instance.

I was hoping this was a common issue that people had faced, but if not I will just take @Nicolas Grossi 's advice and work directly with Adaptavist via an official plugin support request.