Issue Summary

Insight custom field value selection is not retained in Issue navigator when adding an issue type or project filter

Steps to Reproduce

1. Create an Insight object custom field and assign it to one project over several issue types
2. Create some test issue over different issue types in above project and make sure that at least 2 issues have different issue types but same object value selected in the custom field.
3. In Basic Search, first filter by the Insight custom field so that 2 issues are retrieved from 2 different issue types:
   
4. Now select the Issue Type or the project to filter additionally and switch to Advanced search to validate the JQL. Observe that the Insight custom field value selection is cleared and all issue for that Issue type are so retrieved:
   

Expected Results

Insight custom field value selection should be retained in the JQL no matter how it's added to the basic search

Actual Results

Insight custom field value selection is not retained in the JQL if the field and value are added before other search criteria. For example

"Insight field" = AD-7 AND project = ITSD

will become

project = ITSD

when switching to Advanced Search.

However, if the search for the Insight custom field is added last in the Basic search, this behavior is not reproducible.

Here's a quick video to demonstrate the issue: basicSearch.mov

Workaround

Use Advanced search or select/filter the Insight custom field(s) last

Notes

• Tested with more than 1 Insight custom field in the JQL, all search criteria related to Insight custom fields are removed if these were added before other search criteria for non-Insight custom fields
• Tested with other custom field types (like Team field from Advanced Roadmaps) and also from third-party plugins, issue is not reproducible and only Insight custom fields are removed
• Tested with a standard Jira custom field (e.g. Select list). The search criteria doesn't get removed regardless of the sequence of adding the search criteria in Basic search