Default search JQL query changed from text
Asked by Andras Gombos:

My org uses Jira Cloud (Premium). Over the last couple of weeks, the default search JQL query changed.

This is the one that loads when the top right search bar is used:

![jirasearch.png](/t5/image/serverpage/image-id/339129i5EB0AA9BD8961D25/image-size/large?v=v2&px=999 "jirasearch.png")

#### Past setup {#toc-hId-350377179}

```
text ~ "searchterm*" ORDER BY Created DESC
```

#### Current setup {#toc-hId--1457077284}

```
summary ~ "searchterm*" OR description ~ "searchterm*"?ORDER BY Created DESC
```

These yield two very different results. Most importantly, the past setup query, searches in custom fields. The new query does not.

Can this behaviour which worked well and changed without any notice be customised / reverted / opted out of?


Answers:
author: Bill Sheboy
body: Hi [@Andras Gombos](/t5/user/viewprofilepage/user-id/4202213)

I believe that change started rolling out at the end of June 2024:

<https://confluence.atlassian.com/cloud/blog/2024/07/atlassian-cloud-changes-jun-24-to-jul-1-2024#AtlassianCloudchangesJun24toJul1,2024-ImprovedsearchusingsummaryanddescriptionfieldsFD-63933>

Based on this week's blog entry, the change is still rolling out.

Kind regards,  
Bill


author: Marc - Devoteam
body: Hi [@Andras Gombos](/t5/user/viewprofilepage/user-id/4202213)

I can still search on text \~, tried it on multiple instances, free, standard and premium.

So I can't reproduce you issue.

I have used the view all issues option and the main seachbar option.

Used as JQL text \~ and in the searchbar just enter the searchterm and it will use the clause text \~ "searchterm"

If this doesn't work on your instance, please contact Atlassian Support

comments: author: Andras Gombos
body: Hi Marc, I'm not sure we're talking about the very same use case.

Let me adjust the replication steps.

1. Open the instance
2. Enter a search term into the search field up top
3. Press Return

Of course if you go by the Filters main nav option and below that the "View all issues" option as you describe, you can set up the text JQL operator.

It's not about whether the text operator can be used at all. It's about what's the default when submitting a term from the search bar.

It is a very distinct and unilateral change and I see no way to adjust the settings.


author: Marc - Devoteam
body: hi [@Andras Gombos](/t5/user/viewprofilepage/user-id/4202213)

If you use the main search option, just enter your search term, you don't have to provide the clause "text \~"

This will search any text based field, even comments. I have tested this on multiple instances.


author: Andras Gombos
body: HI [@Marc - Devoteam](/t5/user/viewprofilepage/user-id/3796976), thanks for the feedback.

I'm saying that the option you describe unequivocally brings this result to me and everyone else in our Jira instance:

```
summary ~ "searchterm*" OR description ~ "searchterm*"?ORDER BY Created DESC
```

And not what it did earlier, which is the desired setting:

```
text ~ "searchterm*" ORDER BY Created DESC
```

Hope this makes sense.

I have now tried to set Basic search instead of JQL. The prompt came up:

![SCR-20240731-oeii.png](https://community.atlassian.com/t5/image/serverpage/image-id/339145i48AA183DC8471BB1/image-size/large?v=v2&px=999 "SCR-20240731-oeii.png")

And then:

![SCR-20240731-oejd.png](https://community.atlassian.com/t5/image/serverpage/image-id/339146i69FD2227225C986F/image-size/large?v=v2&px=999 "SCR-20240731-oejd.png")

So, this is proof. It is a "feature", unprompted and unilateral, with no way to revert.

Maybe it's a phased rollout, which is why you may not see it in action yet.


Tags: cloud

jira-cloud