Confluence Search: Why does the workaround with RegEx for leading wildcards not work?

Katharina Bender
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 15, 2023

In Page Confluence Search Syntax | Confluence Data Center and Server 8.2 | Atlassian Documentation is written that Lucene doesn't allow wildcards in the beginning of your search, but you can format your search as a regular expression as a workaround. For example, you can't search for *hum* or ?hum*, as they begin with a wildcard, but you can search for /.*hum.*/ and find things like hum, human, and inhumane.

 

I want to get "Diktierleiste" with /.*leiste.*/, but this is not working. 

2 answers

0 votes
C_ Dicker September 5, 2023

I also tested the workaround and it failed. No idea if it really works.

0 votes
Brant Schroeder
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
August 28, 2023

@Katharina Bender Welcome to the Atlassian community

I would suggest searching for Diktie.*/  Then the end is the wildcard.

Suggest an answer

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

Atlassian Community Events