The basic question: Is there a way to do a wildcard search of a list rather than just in a text field. We are maintaining several major releases of software at a time(when a big customer says NO to the next major release and pays for support on the current release, who are we to say). i.e. example of unreleased versions:
12.0.3, 12.0.4, 12.1.1, 12.2.0
My PV manager wants to create a wildcard of only the 12.* versions. Currently, the only way to get around this is to individually list each of the 12 versions. i.e.
AND fixVersion in ("12.0.0", "12.0.1","12.0.2")
If I try 'AND fixVersion in ("12.*")', it results in the error: The value '12.*' does not exist for the field 'fixVersion'.
This is a pretty basic search capability so I'm hoping, it's just a misunderstanding on my part.
Thanks, the above worked for me as well, however I was trying another trick but didn't work
issueFunction in issueFieldMatch("labels = <myLabel>", "fixVersion", "FY-18 *")
It errors saying couldn't find the fieldname fixVersion, whereas it's a valid field. Has anyone tried this to do wildcard search in non-text fields
Syntax - issueFieldExactMatch
issueFieldExactMatch (subquery, fieldname, regexp)
From JIRA 4.3 onwards you can use ff:12* (for Fix For Version) and v:12* (Affects Version) in the Quick Search box (http://confluence.atlassian.com/display/JIRA043/Using+Quick+Search), but it looks like this is not impemented in JQL yet and is an open feature request (https://jira.atlassian.com/browse/JRA-24152)
Wildcard searches are available in JQL (http://confluence.atlassian.com/display/JIRA043/Advanced+Searching#AdvancedSearching-CONTAINS), but only for free text fields.
Hope that's of some help,
Thanks for the quick reply but it misses the mark.
The Quick Search method is more of a macro that substitutes the current list of 12.* versions into the search of affectedVersion or fixVersion lists. I can't save it as a dynamic filter but rather a hardcoded list of versions at the time I involved the Quick Search.
As for CONTAINS, as you stated, it only works for text based fields.
I'll left this query open for a while, in hopes that someone can propose a workaround.
BTW, I voted for JRA-24152, thanks
• Find issues affected by versions that ther name starts with 'v1' i.e. 'v1.1.0', 'v1.2', 'v1.1.6', etc:
• Find issues fixed in versions that ther name contains 'alpha':
• Find issues affected by versions that ther name starts with 'SNAPSHOT' i.e. 'v1.1-SNAPSHOT', 'v1.5-NIGHTLY_SNAPSHOT', etc:
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
Hello! I'm Rayen, a product manager at Atlassian. My team and I are working hard to improve the trial experience for Jira Software Cloud. We are interested in talking to 20 people planning t...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs