Loading...

XML

Word

Printable

Details

Type: Bug
Resolution: Done
Priority: High
Fix Version/s: 8.20.5
Affects Version/s: 3.13, 6.3, 7.2.14, 8.20.11
Component/s: Administration - Workflows, Email notifications, Issue - Actions
Labels:

Introduced in Version:
3.13
Support reference count:
15
Symptom Severity:
Severity 2 - Major
UIS:
94
Bug Fix Policy:
View Atlassian Server bug fix policy

Description

The problem is that presently the issue event is actually fired from a Workflow post function.

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.

Attachments

Issue Links

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...

mentioned in: Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...

(4 mentioned in)

Activity

People

Assignee:: Unassigned

Reporter:: Mark Lassau (Inactive)

Votes:: 98 Vote for this issue

Watchers:: 63 Start watching this issue

Dates

Created:: 29/Oct/2014 12:04 AM

Updated:: 11/Jul/2023 9:04 PM

Resolved:: 08/Dec/2022 8:38 AM