It has been solved. Because I used the issue listener, when the page was doing Update issue, I was also doing Delete issue in the listener, resulting in the conflict between the two actions and locking the table
The REST API has nothing to do with the UI.
Could you explain in more detail what you are doing, and what the problem actually is?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The custom IssueEventListener listener is created. The current work order is modified through the REST API in the listener, causing a transaction conflict and locking the Project.issue table
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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?)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.