Parsing rules fix filter

[yasta5]

Contributing to Cortex XSOAR Content

Make sure to register your contribution by filling the contribution registration form

The Pull Request will be reviewed only after the contribution registration form is filled.

Status

• In Progress
• Ready
• In Hold - (Reason for hold)

Related Issues

fixes: https://jira-hq.paloaltonetworks.local/browse/XSUP-26041

Does it break backward compatibility?

• Yes
  • Further details:
• No

[anara123]

I am going to ForceMerge since the PR fails on unrelated unit tests.

=========================== short test summary info ============================
FAILED Utils/github_workflow_scripts/github_workflow_scripts_tests/link_pr_to_jira_issue_test.py::test_trigger_generic_webhook[True-expected0] - requests_mock.exceptions.NoMockAddress: No mock address: POST http://test.com/instance/execute/GenericWebhook_link_pr_to_jira
FAILED Utils/github_workflow_scripts/github_workflow_scripts_tests/link_pr_to_jira_issue_test.py::test_trigger_generic_webhook[False-expected1] - requests_mock.exceptions.NoMockAddress: No mock address: POST http://test.com/instance/execute/GenericWebhook_link_pr_to_jira
================== 2 failed, 90 passed, 222 warnings in 4.20s ==================

Both of these unit tests are handled in different issue

[evisochek]

I am going to ForceMerge since the PR fails on unrelated unit tests.

=========================== short test summary info ============================
FAILED Utils/github_workflow_scripts/github_workflow_scripts_tests/link_pr_to_jira_issue_test.py::test_trigger_generic_webhook[True-expected0] - requests_mock.exceptions.NoMockAddress: No mock address: POST http://test.com/instance/execute/GenericWebhook_link_pr_to_jira
FAILED Utils/github_workflow_scripts/github_workflow_scripts_tests/link_pr_to_jira_issue_test.py::test_trigger_generic_webhook[False-expected1] - requests_mock.exceptions.NoMockAddress: No mock address: POST http://test.com/instance/execute/GenericWebhook_link_pr_to_jira
================== 2 failed, 90 passed, 222 warnings in 4.20s ==================

Both of these unit tests are handled in different issue

The issue was fixed here:
#28033
no need to force merge