Issue Summary

This is part of a multi pronged error and Feature set of issues please review this video of the overall behavior that details what is occurring and why it is important:

• https://www.loom.com/share/190469b2eff7490d993b21e63f4e8a2a?sid=42823fe9-bd56-4a58-9edc-656d8d53f080

This specific BUG in the set is related to Jira components and Compass components with the same name breaking Search capabilities, as a Compass Component is visible in the Field but not searchable in JQL

Steps to Reproduce

1. Create a Jira component called "Example"
2. Create an issue add component "Example" to the issue
3. Switch to Compass components
4. Create a compass component called "Example"
5. Add that component to a different issue
6. Open Legacy Advanced issue search in one tab
7. Open the New issue search experience in another tab
8. use the following 2 searches in both locations

   project = "YOU PROJECT NAME" and component = "Example"
   

   project = "YOU PROJECT NAME" and component != "Example"
   

Expected Results

1. Both issue are returned in each tab when the = "Example" operation is used
2. Neither issue is returned in either tab when != "Example" operation is used

Actual Results

Option 1 and 2 expected results occur for legacy Advanced issue search

However in the New issue search Only 1 issue is returned by each of the two search terms "=" and "!=" as the search is only displaying the Jira component results and ignoring the compass component but still displaying the value in the component field causing confusion to end users

Workaround

Use Unique names for Jira and compass components, Noting New search will display values for component but will not allow you to search for them so you will have to use Legacy search to search for Compass components
Switch to legacy search by:

• Select Filters > View all issues
• Select the 3 dot "..." meatball menu icon in the upper right
• Select "switch to Old search experience"

Please refer to This Video for a full breakdown of how the overall issue is affecting your system to understand how to identify which issues are in what component category