-
Bug
-
Resolution: Done
-
High
-
3.13, 6.3, 7.2.14, 8.20.11
-
3.13
-
15
-
Severity 2 - Major
-
94
-
The problem is that presently the issue event is actually fired from a Workflow post function.
See also discussion in JRA-31733
Notes
For apps observing this issue, an available alternative is to use the OnCommitIssueEventBundle (https://docs.atlassian.com/software/jira/docs/api/latest/com/atlassian/jira/event/issue/commit/OnCommitIssueEventBundle.html) instead of the onCommitIssueEvent.
Solution
Fire event post functions in Workflows creates 2 events. The first one, IssueEvent, is fired during the execution of post function. The second, IssueChangedEvent, is fired after the transaction is commited. Listeners need to receive IssueChangedEvent or OnCommitIssueEventBundle events after successful commit.
- is related to
-
JRASERVER-67880 Wrong data can be cached in Jira while in post function creating issue or changing label custom field value
- Closed
- relates to
-
JRASERVER-34376 Issues not committed to database (and cannot be fetched) at time of event dispatch for issues created from post function
- Gathering Impact
-
JRASERVER-31733 Run all issue event listeners inside the database transaction that writes the issue data
- Closed
- causes
-
PSR-313 Loading...