Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Better support for the ~ in JQL

Fix versions

None

Priority

Description

For the moment, customers can't filter with partial contents of our Jira custom field.

The attached case requests that we support `~` with wildcards, as fixVersions does it.

Adrien’s opinion

I have looked into it back in the time when I implemented the custom field, and I didn’t find the right Searcher class from Jira to implement, if I wanted to support the ~ operator. Maybe another developer will be more lucky, but my conclusion is that it was impossible for me.

Confluence content

mentioned on

Activity

Show:

Andrii TyranovetsOctober 31, 2024 at 4:49 PM

I have a couple points regarding this operator:

  1. There’s a custom function (requirementYogiKeys()) which does exactly what is expected of the ~ operator (see com.requirementyogi.datacenter.jiraapp.jql.function.RYRequirementsWithBaselineFunction);

  2. The limit of the items in the results of the function is set in the constructor. It it a Confluence default 1000 items but it will be easy to change to any other number. While it may not make a lot of sense to change it to any different arbitrary item it may be an option to add a limit as a field in the settings for customers to set themselves;

  3. If the function is not sufficient then it would worth it to try to implement the functionality as a ~ operator

Details

Assignee

Reporter

Sprint

Labels

Requirement Yogi

Created October 19, 2023 at 3:04 PM
Updated January 2, 2025 at 8:41 AM
Configure