-
Suggestion
-
Resolution: Unresolved
-
None
-
1
-
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
But overall the following bugs can be created as a result of allowing A Compass Component to be created that has the same name as an Existing Jira Component or vice versa
Ultimately When a project is set to use compass components the New Issue Search functionality shows Compass components names in quick tip search results and has a easy method for end users to follow to erroneously create a duplicate that cannot be found by that JQL search
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
- causes
-
JSWCLOUD-27497 Compass component with the same name as Jira component causes bad search results
- Gathering Impact
-
JSWCLOUD-27498 Editing a Jira component name that has a Compass Duplicate duplicate will show incorrect results
- Gathering Impact
- is related to
-
JSWCLOUD-26878 Enable Jira Components and Compass to be used in parallel
- Gathering Interest
- relates to
-
JSWCLOUD-27501 Cannot Search for compass Components In new Issue search experiance
- Short Term Backlog