-
Bug
-
Resolution: Timed out
-
Low
-
11
-
Severity 3 - Minor
-
NOTE: This bug report is for JIRA Cloud. Using JIRA Server? See the corresponding bug report.
Summary
After configuring the default configuration scheme for a Custom Field with context defined for all issue types and all projects, if performing a search filtering for that Custom Field using Basic Search, the following message is returned: "Field is not applicable for the current project and/or issue type"
Steps to Reproduce
- Go to Administration > Issues > Custom Fields
- Add a Custom Field named "Test"
- Navigate to that Custom Field, then go to Cog Icon > Configure
- Edit the Applicable contexts for scheme with the following:
Issue Types: Any issue type
Check "Apply to issues under selected projects" then select all projects. - Try searching for issues using that Custom Field on Basic Search
Expected Results
No warnings about the context of that Custom Field
Actual Results
A warning is shown on the UI: "Field is not applicable for the current project and/or issue type".
Workaround
Using Global context on the Custom Field configuration makes the behaviour not reproducible anymore.
- is related to
-
JRACLOUD-71320 Fields cannot be queried via Basic search
- Closed
-
JRASERVER-59032 Custom Field context not behaving correctly.
- Gathering Impact
- relates to
-
CONFCLOUD-74104 Non-global context custom fields won't display in JIRA events with a JQL with multiple projects
- Closed
- mentioned in
-
Page Loading...