Details
-
Bug
-
Resolution: Fixed
-
Low
-
5.2
-
None
-
5.02
-
Description
The problem in particular is that indexing an issue in JIRA happens due to an event listener listening to an issue event. Publishing webhooks also happens as the result of an event listener listening to an issue event. The order in which listeners get notified of these events is not deterministic however! So it can happen that sometimes the webhook publisher will be notified first and try to run the JQL filter before the issue has been reindexed!
Steps to reproduce:
- Setup a webhook with JQL filter
- Setup a listener for the webhook so you can check if the webhook gets sent (I just used tcpmon to proxy the request from port 8989 to port 80 on my local box)
- Create an issue (or whatever) to trigger the webhook
Sometimes no webhook will be sent. You can also simulate this by setting a breakpoint in the IssueIndexListener, thus simulating a slow index operation.
Attachments
Issue Links
- is caused by
-
JRASERVER-26058 IssueIndexListener indexing stale data
- Closed
-
JRADEV-18128 Loading...
- is related to
-
JRASERVER-30811 delete issue event does not play well with webhooks when using JQL filters
- Closed
-
JRASERVER-30849 Webhook (or event?) should fire as the last step in issue creation/updation
- Closed
- relates to
-
JRASERVER-24107 Improve the behaviour of indexing after a workflow transition
- Closed
-
JRA-24107 Loading...
-
JRADEV-16117 Loading...
- copied from
-
JRADEV-16099 Loading...
- has Epic
-
JRADEV-15927 Loading...
- is derived by
-
JRADEV-16150 Loading...
- is detailed by
-
EVENT-18 Loading...