Logistics filter returns incorrect results with Connections item appearing first

[PedroAntunesCosta]

Description

Filtering known issues by the "Logistics" category returns incorrect results. The first result displayed is tagged as "Connections" instead of "Logistics", indicating a filtering logic error.

Steps to Reproduce

1. Navigate to the Known Issues page at https://help.vtex.com/known-issues
2. Click the "Filters" button
3. Select "Logistics" from the Modules checkbox list
4. Click "Apply filters"
5. Observe the filtered results

Expected Behavior

All displayed results should be tagged with "Logistics" category.

Actual Behavior

The first result in the filtered list is "Amazon order does not integrate correctly" which is tagged as "Connections" instead of "Logistics". Subsequent results correctly display "Logistics" tagged items.

Screenshots

Investigation Notes

Related Files

• The filtering logic is implemented in src/pages/known-issues/index.tsx at lines 89-112
• Module filter configuration is defined in src/utils/constants.ts at lines 302-411
• The Filter component that handles user interactions is located in src/components/filter/index.tsx
• Known issue data is parsed from frontmatter in src/pages/known-issues/index.tsx at lines 253-273

Suggested Investigation Paths

• Examine the filtering logic in src/pages/known-issues/index.tsx lines 89-112, specifically the module filter check at line 95: filters.modules.includes(knownIssue.module)
• Review the module name-to-ID mapping logic at lines 84-87 and 175-177 in src/pages/known-issues/index.tsx
• Verify that the module field extracted from frontmatter (line 262) matches the expected filter values defined in src/utils/constants.ts
• Check if there are data inconsistencies where known issues have incorrect tag values in their frontmatter
• Compare the filter application logic in src/components/filter/index.tsx lines 170-179 to ensure selected filter IDs are correctly mapped

Potential Root Causes

• Mismatch between filter option IDs and actual module values in known issue data
• Incorrect mapping when converting filter selection names to IDs
• Data inconsistency where some known issues have incorrect category tags in their frontmatter
• Filter logic may not be correctly excluding items that don't match the selected category

Additional Context

The issue affects the user experience when filtering known issues by category, as users expect to see only items matching their selected filter criteria.

[PedroAntunesCosta]

Jira issue created:
EDU-16834