Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

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

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?

1 answer

0 votes
Ram Kumar Aravindakshan _Adaptavist_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Mar 24, 2023

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,


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.

Like Nicolas Grossi likes this

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events