Issue Summary

In JCMA 1.10.18, we introduced entity level preflight cache.

The caching happens at issue level. If there are any changes to the issue, the cache gets invalidated.

However, if a new user has just voted or watched an issue, the cache doesn't get invalidated. So, if the user is invalid or duplicate, preflight would skip catching the failure.

For this issue to happen, the below conditions need to happen -

• Cache is already created and has not expired for the project

• A new user votes or watches any of the issues in the project

• The new user is invalid/duplicated

• The new user hasn't already performed any other activity (e.g. created/edited issue, comment, etc.) on that project.

This is reproducible on Data Center: Yes

Steps to Reproduce

• Create a project and and issue
• Create a migration plan selecting referenced users mode
• Run preflight checks
• Create an invalid user
• Login using invalid user and watch and vote on the issue
• Login as admin user again and run preflight checks again

(Test cases 8 and 9 on https://hello.atlassian.net/wiki/spaces/MigPT/pages/3566381159/Test+Cases+Entity-Level+Caching)

Expected Behaviour

The preflight check should detect invalid user and fail.

Observed Behaviour

The preflight check succeeds.

Workaround

Manually invalidate the cache - https://hello.atlassian.net/wiki/spaces/MigPT/pages/3552622174