-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Medium
-
None
-
Affects Version/s: 9.2.0, 9.3.0, 9.4.0, 9.4.2, 9.12.0
-
Component/s: Issue - Fields
-
None
-
9.02
-
7
-
Severity 3 - Minor
-
1
Issue Summary
This is reproducible on Data Center: Yes
The component field values selected under more options are not saved, and getting reset to default when other fields (like issue type, date, etc) values are changed. This behavior is impacting saved filters.
when using the search engine, all previously checked components disappear. If they are checked by search, and the user clicks out of the component select window, all changes disappear and go back to one default component.
same behavior observed in Advanced search, even if changes in basic are made only related to issue type, date, etc.
Please note reported issue is not observed in earlier Jira versions 8.20 / 9.0/9.1
Steps to Reproduce
- Create more than 300 components under a Jira software project
- Move to "search issues" under issues, add the component field to filter search, and select one of the values under "xxx more options, continue typing to refine further"

- Component field selected values are not saved

4. Change other field values will reset the component field to default "All"

Expected Results
Component field search should retain values
Actual Results
The component field gets reset to the default value.
Workaround
Currently, there is no known workaround for this behavior. A workaround will be added here when available
- is related to
-
JSDSERVER-8702 Insight custom field value selection is not retained in Issue navigator when adding an issue type or project filter
-
- Gathering Impact
-