-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
1000.5.0 Cloud, 6.4.4, 7.0.0
-
6.04
-
3
-
Severity 3 - Minor
-
NOTE: This bug report is for JIRA Server. Using JIRA Cloud? 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.
- relates to
-
JRACLOUD-59032 Custom Field context not behaving correctly.
-
- Closed
-
-
JRASERVER-69731 Enabling a second context for a custom field causes the default behavior to no longer function.
-
- Closed
-
- causes
-
JSP-409404 Loading...