Jira Issue Macro JQL Username is Changing and Breaking Search

Summary

Cloud Customers who are using the Jira Issue Macro with a JQL Filter based on Username "was in" are noticing that the Username is being converted to an ID after it is saved

The JQL does not run as it appears to be invalid

Steps to Reproduce

1. Create a Page (or view an existing page) and add a Jira Issue Macro with a Username filter; ex: assignee was in (some.user)
   
2. Insert the Macro and Publish the Page
3. Edit the Page and Macro Again

Expected Results

Macro shows the results

Actual Results

When Viewing the page, the following message is shown:

JIRA project doesn't exist or you don't have permission to view it.

View these issues in JIRA

If the Macro is edited, a different error is shown

The JIRA server didn't understand your search query. If you entered JQL, please ensure that it's correctly formed. If you entered an issue key, ensure that it exists and you have permission to view it. Learn More

Notes

The ID shown appears to be the User's Atlassian account ID
It only appear to be affecting the "was in" query, using assignee = some.user or assignee in (some.user) seems to work with the Atlassian account ID
assignee = ID

assignee in (ID)

Workaround

If using "Was In" JQL, create and save the Filter in Jira; rather than specifying JQL in the Jira Issue Macro, use the saved filter; ex filter = "My Saved Filter"