WARNINGS in JSM log - ISSUE with id=xxxxxx should have a version by now although all issues have versions

Issue Summary

With JSM 5.5 log4j v2 causes houndreds of WARN logs for any action that triggers indexing on issues. (edit/comment etc).
The logs state that issue should have a version by now. This is misleading as all issues have versions.

This is reproducible on Data Center: (yes)

Steps to Reproduce

1. Install JSM 5.5 or later
2. Create a JSM Project and comment

Expected Results

No WARN messages for the index operation happens if issue has a version.

Actual Results

Issue indexer thread throws WARN messages multiple times for every edit

2023-03-10 15:45:22,450+0000 SdSerialisedOffThreadProcessor:thread-4 WARN admin     [c.a.j.issue.index.DefaultIssueIndexer] ISSUE with id=10201 should have a version by now
2023-03-10 15:45:22,644+0000 SdSerialisedOffThreadProcessor:thread-4 WARN admin     [c.a.j.issue.index.DefaultIssueIndexer] ISSUE with id=10201 should have a version by now

How to validate if all issues have versions?

We are aware of the issue causing JSM code to produce misleading logs.
In case the log is coming from threads:

• PsmqAsyncExecutors-job
• SdSerialisedOffThreadProcessor
• http-nio threads from greenhopper rest endpoints

It is very likely that the log is misleading and in fact all issues have an issue version.

To further validate you can run a following query:

select count(*)
from jiraissue
         left join issue_version on jiraissue.id = issue_version.issue_id
where issue_version.issue_id is null;

The correct result should be 0. In case it is more than 0 Jira is in inconsistent state and requires further diagnosis.

Workaround

Currently, there is no known workaround for this behavior. A workaround will be added here when available