Summary

Logging work on a issue transition creates duplicate "history" entries in the database. The Issue History shows duplicate entries for the transition.
The "Transitions" issue tab displays an incorrect amount of Execution Times.
This affects scripts or plugins using the history to reconstruct status changes.

Environment

• JIRA Core

Steps to Reproduce

1. Add the "Log Work" field to a transition screen.
2. Run the transition on an issue and add some work time.
3. Navigate to the History tab on the issue

Expected Results

Work logged and Status changes show only once.
The change is only stored once in the database.

Actual Results

The History shows 2 entries with the exact same date and time for the same transition.

The database shows a duplicate entry for the transition in the 'changeitem' table with a time difference of ~0.1 seconds
The Transitions tab shows Execution Times = 2 for that transition.

Notes

Changelog entries can be found for a specific issue with: (replacing <PROJECTKEY> and <ISSUENUM> )

select * from changegroup g left join changeitem i on g.id = i.groupid where issueid = (select id from jiraissue where issuenum = <ISSUENUM> and project = (select id from project where pkey = '<PROJECTKEY>')) order by created asc;

Workaround

To prevent duplicate entries, remove the "Log Work" field from the Screen used in the transition and log work separately using the More (...) -> Log Work option.