Listener got wrong issue key(parameters)

I've got some problems when using script-runner 3.1.4

I try to create 100 issues in concurrency 10 and put a script listener to listen "Issue Created" event.

Then I found listener always got same issue key. ex. There should be totally 100 issue key printed out. But only 34 issue key presented in log file and total printed lines were exactly 100.

I thought maybe all creating issue had successfully triggered the listener. For unknown reason, listener always got previous issue key.


Is there anyone who can tell me how to resolve it?

2 answers

Sounds odd, but can you try with the latest version to check that it hasn't been fixed.

Yes, I tried version 4.1 and this problem didn't happen! But version 3.1.4 was the latest free version...

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 29, 2018 in Marketplace Apps

How to set up an incident workflow from the VP of Engineering at Sentry

Hey Atlassian community, I help lead engineering at Sentry, an open-source error-tracking and monitoring tool that integrates with Jira. We started using Jira Software Cloud internally last year, a...

1,701 views 3 11
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you