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

Duplicate Scriptrunner log entries from the console


I am getting immediate duplicate log entries from running scripts from the script console. This may be happening from listeners as well I have some cases it seems to but I can't 100% replicate.

I only have a single line that would print to the log that is not in a loop, unsure how this happening, I'm guessing the logging module is being loaded twice somehow?

Could someone please point me in the right direction?

Screen Shot 2021-02-17 at 5.13.14 PM.png

Screen Shot 2021-02-17 at 5.12.50 PM.png

1 answer

1 accepted

4 votes
Answer accepted

Adding this line fixed it.


Not sure why though, this seems like new behavior to me.

I thought this was the answer, I sat back down this morning, and now I get no results in my log.

I had to remove this line I added to get any log results, however yesterday, I had to have this line to remove duplicates. Nothing in the environment has changed to my knowledge.

Now, I am truly perplexed.

Did you ever find a solution for this? I'm now seeing the same thing with my Scriptrunner logs and I can't figure out why it's happening.

[Edit: We ended up bouncing our Jira instance and that solved it. Strange]

@Tom Hudgins 

Sometimes I noticed when I was changing something and had a "blip" (Lets be technical here) or an overflow that didn't actually crash everything these process threads would sometimes end up "stuck" open somehow and a bounce usually fixed the issue. I remember at one point it was either 2 lines for every entry or no lines.. and I think that's when the bounce fixed it for us.

Not a very technical answer, but it's been quite some time since I've experienced this or remember this particular issue. Just trying to do a bit of recall here.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events