The current jql when selecting "Search work items" is 

created >= -30d order by created DESC

For most users, this pulls up 50 of 1000+ issues and is both not what is needed and is slow.  My suggestion is that it either not execute the search or execute a search that returns nothing such as 

created >= 1d

This would pull up much faster and allow a user to start editing the jql faster.  If that is determined to be not as generally usuable, perhaps it could do someting that pulls up a smaller data set more focused on the user such as 

created >= -1d and assignee=currentUser()

 

This is actually a suggestion for Jira Cloud, but I couldn't select that, so if possible, please move this to JIRACLOUD.