bugfix/FOUR-26348-b: REOPENED The status filter doesn't work when filtering two statuses.

[CarliPinell]

Solution

• The clear button was fixed, removing all previous filters set when it is clicked.
• The "And" logic operator in Status column was hidden.
• The "In" operator also hides "And" logic operator in Status Column
• Al combinations with status "In Progress", "Self Service" and "Completed" are working correctly in Status filter

How to Test

• Go to Inbox
• Select Status column and select combined status "IN PROGRESS" OR "COMPLETED"
• Tasks with both status must be shown
• Open Satus filter and Click CLEAR
• Only In Progress tasks must be shown

Related Tickets & Packages

• https://processmaker.atlassian.net/browse/FOUR-26348

Code Review Checklist

• I have pulled this code locally and tested it on my instance, along with any associated packages.
• This code adheres to ProcessMaker Coding Guidelines.
• This code includes a unit test or an E2E test that tests its functionality, or is covered by an existing test.
• This solution fixes the bug reported in the original ticket.
• This solution does not alter the expected output of a component in a way that would break existing Processes.
• This solution does not implement any breaking changes that would invalidate documentation or cause existing Processes to fail.
• This solution has been tested with enterprise packages that rely on its functionality and does not introduce bugs in those packages.
• This code does not duplicate functionality that already exists in the framework or in ProcessMaker.
• This ticket conforms to the PRD associated with this part of ProcessMaker.

ci:deploy

[processmaker-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarQube

[eiresendez]

This branch is currently 193 commits behind develop, which makes the PR diff outdated and blocks an accurate code review. @CarliPinell Please merge the latest develop into bugfix/FOUR-26348-b and push the result, or create a new PR from an updated branch if that produces a cleaner diff; once the PR reflects the current base, I can proceed with the review.

cc: @sanjacornelius