Unable to JQL Search Using Atlassian account ID

Summary

Confluence customers are experiencing an issue in the Jira Issue Macro where the Username in a JQL Filter is being converted to it's Atlassian account ID.
This causes the Jira Issue Macro to fail to load if they use a "WAS IN" condition; example:

 assignee was in (some.user) 

turns into

assignee was in (<RANDOM USER ID>) 

Running this 'AaID' filter in Jira directly does not load results either

Steps to Reproduce

1. Run a "WAS IN" JQL search against a User's Atlassian account ID

Expected Results

Results are returned.

Actual Results

The value '<RANDOM USER ID>' does not exist for the field 'assignee'.

Notes

A JQL query of

assignee in (<RANDOM USER ID>) 

works however it can be a different result set depending on other conditions of the JQL (date, etc)

Workaround

Usernames still work in Jira, but this may affect Saved Filters if those Usernames are converted to their AaIDs