Issue Summary

When a jira:entityProperty module declares a property with type: user and a searchAlias, the JQL issue navigator correctly renders the user operand as a display name chip on first use (resolved from the REST autocomplete cache). However, after a page refresh, the display name is replaced by the raw account ID (e.g. 61361820c425a20068eac5a6). The native assignee field, used with the same account ID in the same query, continues to resolve correctly after refresh.

This makes any saved or shared JQL filter that uses a user-typed entity property alias unreadable after reload — the user cannot identify who the filter is scoped to, undermining the core utility of the feature.

Steps to Reproduce

1. Install an app that declares a jira:entityProperty module with a user-typed indexed property and a searchAlias. 
2. Navigate to the Jira issue navigator.
3. In the JQL search bar, enter a query using both the custom entity property alias and the native assignee field, selecting the same user from autocomplete for both operands: checklistsItemAssignee = <user> AND assignee = <user>
4. Observe that both operands render as chips with the user's display name.
5. Refresh the page (or reopen the URL directly).

Expected Results

Both the checklistsItemAssignee and assignee operands continue to display the user's display name as a chip after page refresh, consistent with how native user fields behave.

Actual Results

After page refresh:

• The assignee operand correctly shows the user's display name.
• The checklistsItemAssignee operand (entity property alias) reverts to the raw account ID (e.g. 61361820c425a20068eac5a6).

The query itself remains valid and returns correct results, but the filter is effectively unreadable.

The following is observed in the browser console log:

No exception is thrown. The issue fails silently. The hydrateJqlQuery GraphQL resolver returns an empty values array for the entity property alias, while correctly returning the display name for the native assignee field.{{}}

Before refresh, the display name is available from the REST autocomplete cache (/rest/api/latest/jql/autocompletedata/suggestions). After refresh, that cache is gone and the only resolution path is the hydrateJqlQuery GraphQL resolver — which does not support entity property search aliases declared with type: user.

Workaround

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