The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

JQL - componentMatch does not work with number + *

Hwarang Kim
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!
October 12, 2016

Hi team,

 

One of our user request that "componentMatch" does not work properly.

Below are the JQL that my user used.

project = "Q Event 16" AND component in (componentMatch("55UJ5*"))
project = "Q Event 16" AND component in (componentMatch("55UJ6*"))
project = "Q Event 16" AND component in (componentMatch("55UJ7*"))

All three JQL queries show same result, so it looks like number + * does not work properly.

Our component looks like this "55UJ650V-ZA.AEUYLHX_SW_VAL(1)_Software_1610-00068".

 

Does anyone know why it works like this, and how to get proper result?

Thank you.

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

Post a new question

2 votes
Petar Petrov (Appfire)
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
October 13, 2016

See the documentation for ScriptRunner. You should be using Java regular expressions.

If you want to match a beginning of string you should use:

componentMatch("^55UJ5.*")

You can use this online tester to check your regular expressions.

JamieA
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
October 13, 2016

Exactly right, thanks Petar. Unfort it's a bit confusing because it's different from the wildcards used elsewhere in Lucene.