The JQL autocomplete in Jira Cloud suggests textfields ~ when users start typing a full-text search. However, textfields searches fewer fields than the official text operator — it does not include comments and custom text fields, while text does.

This leads to a critical usability problem: users who follow the autocomplete suggestion will receive fewer search results and may miss important issues that contain the search term in comments or custom fields.

Steps to reproduce:

1. Open the JQL editor in Jira Cloud

1. Start typing a full-text search (e.g. textf...)

1. Select the autocomplete suggestion textfields

1. Run the query and note the number of results

1. Replace textfields with text and run again

1. Observe that text ~ returns more results

Expected behavior:
The autocomplete should suggest text ~ as the primary full-text search operator, as it is the official, documented, and more comprehensive option.

Actual behavior:
The autocomplete suggests textfields ~, which returns fewer results and is not the recommended operator.

Impact:
High – every Jira Cloud user who relies on autocomplete for full-text search may miss relevant issues without knowing it.