Recently, a user wanted to link to an epic via the Epic Link field. Clicking on the field's down arrow produced a huge list of possible epics to link to. The user then thought to type in a subset of the Epic name to narrow the list. Epics starting with [T] were not returned when entering a "[" or "T" or "[T]". Searching for Spartacus also had no hits when using S, Sp, Spa, Spar etc. The user had to use the whole word "Spartacus" to get anything returned.
Then I remembered Jira uses a form or regex, regular expressions and, as Admin, tried \[, \T and \[T\] - all of which returned matches. Likewise, using S*, Sp*, Spa*, etc all had matches of various degrees of usefulness.
Am I mis-interpreting what is actually going on here or is there something else in play that would result in the return an empty list of possible epics to link to?
Can anyone tell me, when trying to link to Epics via the Epic Links field by entering a partial Epic name into the Epic Links field - it is now necessary to use Lucene query parser syntax? Has it always been like this or did something change? I'm asking because it seemed, not too long, that query parser syntax was not needed to produce a more focused list of possible epics to link so
Thank You,
Jim
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.