You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I'm sorry, I need more explanation.
A listener will pick up an event and (maybe) make a change to an issue. A REST API call will ask a system to do something.
Even if someone clicks edit at the same time that one or both of those are running, they'd need to be doing it within microseconds of the other actions for a conflict to happen, and even then, Jira would just sequence the changes as they arrive.
So, I am a bit stuck on what the problem is.
What do you get on screen when you have a "transaction conflict"? What do you mean by "locking the project.issue table" (there isn't a project.issue table, and more importantly, are you actually looking at the database? Why?)