Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
  • Community
  • Q&A
  • Jira
  • Questions
  • JQL query for search issues based on substring as wildcard * can’t be used as first character

JQL query for search issues based on substring as wildcard * can’t be used as first character

Stefano Astuti November 21, 2025

The first screenshot shows the list of issues and their descriptions.Screenshot 2025-11-21 143955.png

I’m trying to filter issues based on a substring inside text fields, but the JQL behavior seems limited. 

project = TEST AND textFields ~ "JIRA"

I only get issues where the text contains the exact word “JIRA”. (second screenshot)Screenshot 2025-11-21 144255.png

If I run:

project = TEST AND textFields ~ "JIRA*"

I get issues where a word starts with “JIRA” (e.g., JIRACON). (third screenshot)Screenshot 2025-11-21 144311.png

What I cannot do is search for issues where “JIRA” appears inside a longer word
(e.g., CONJIRATEST, ABJIRAXYZ), because JQL does not allow leading wildcards

Is this the expected behavior of Jira full-text search?
Is there any built-in way in Jira Cloud to filter issues where a substring (e.g., “JIRA”) is contained inside a word?

2 answers

1 accepted

0 votes
Answer accepted
Jack Brickey
Community Champion
November 21, 2025

Hi @Stefano Astuti , to achieve this you would need a JQL search extension addon, e.g. JQL Search Extension or similar . Check the Marketplace and give one a try. Alternatively, if this is a frequent need, you can always export and search using Google sheets or excel

Stefano Astuti November 25, 2025

Thanks again for taking the time to respond.
I have to say this limitation is quite frustrating, because it prevents very basic searches that one would normally expect to be supported natively (such as finding a substring inside a word).
I understand that an add-on is required, but it would be extremely helpful to have this capability built directly into JQL, without relying on external plugins or exporting data.

Hopefully the Jira team can consider this in the future.

Like Jack Brickey likes this
0 votes
Marc -Devoteam-
Community Champion
November 21, 2025

Hi @Stefano Astuti 

This is expected behaviour.

As mentionec by @Jack Brickey you will need a 3rd party solution for this to achieve your requirement.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events