Issue Summary

When making a search with select cascading custom fields, the following warning may be added to the application logs.

025-03-19 12:59:47,794+0000 http-nio-8080-exec-22 url: /secure/QueryComponent!Jql.jspa; user: admin WARN admin 779x9570x1 1w8snup 10.224.44.23,10.227.170.104 /secure/QueryComponent!Jql.jspa [c.a.j.i.c.searchers.transformer.AbstractCustomFieldSearchInputTransformer] Searcher customfield_10300 (CascadingSelectCustomFieldSearchInputTransformer) tried to search with context it does not exist for. The search context is com.atlassian.jira.issue.search.SearchContextImpl@39713f86[projectCategoryIds=[],projectIds=[],issueTypeIds=[]]

Even though the JQL is well formatted and configuration is valid, this warning may appear.

Steps to Reproduce

1. Install a vanilla instance of Jira Software Data Center.
   • This was validated on versions 9.0.0, 9.4.30, 9.12.17 and 10.5.0.
2. Create a sample software project.
3. Create a select cascading custom field with a context applied only to the software project.
4. Add a few options to the select cascading CF.
5. Go to Issues > Search for issues and change to the Advanced search.
6. Run a search with the following JQLs.

   <cascadingCF> = <valid-option>
   

   <cascadingCF> in cascadeOption("<valid-option>")
   

Expected Results

The search provides the expected results and not warnings are logged on the application logs.

Actual Results

The search provides the expected results.
Warnings are logged on the application logs (atlassian-jira.log) as follows.

2025-03-19 13:14:31,046+0000 http-nio-8080-exec-14 url: /secure/QueryComponent!Jql.jspa; user: admin WARN admin 794x10106x1 1lwbym8 10.224.56.123,10.227.170.104 /secure/QueryComponent!Jql.jspa [c.a.j.i.c.searchers.transformer.AbstractCustomFieldSearchInputTransformer] Searcher customfield_10300 (CascadingSelectCustomFieldSearchInputTransformer) tried to search with context it does not exist for. The search context is com.atlassian.jira.issue.search.SearchContextImpl@2cc16ba7[projectCategoryIds=[],projectIds=[],issueTypeIds=[]]

Adding more clauses to the JQL search, such as project = <project-key>, prevents the warning.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available.