Skip to content

fix(FOUR-34098): allow sorting by case_status in get_all_cases - #9111

Open
gproly wants to merge 1 commit into
developfrom
bugfix/FOUR-34098
Open

gproly wants to merge 1 commit into
developfrom
bugfix/FOUR-34098

Conversation

@gproly

@gproly gproly commented Oct 22, 2026

Copy link
Copy Markdown
Contributor

Replace invalid sortable field status with case_status so Status column sort matches the DB/API field and no longer returns 422.

https://processmaker.atlassian.net/browse/FOUR-34098

Replace invalid sortable field `status` with `case_status` so Status column sort matches the DB/API field and no longer returns 422.

https://processmaker.atlassian.net/browse/FOUR-34098
@cursor

cursor Bot commented Oct 22, 2026 •

Copy link
Copy Markdown

PR Summary

Low Risk
Single-field rename in the sort whitelist; aligns with existing column names and filter/select fields with no auth or data-model changes.

Overview
Fixes 422 errors when sorting the cases list by Status in get_all_cases (and related list endpoints that share CaseApiRepository).

The allowed sortBy field was status, but queries and selected columns use case_status. sortBy now whitelists case_status instead of status, so Status-column sort requests pass validation and order on the correct column.

Reviewed by Cursor Bugbot for commit dcc1fea. Bugbot is set up for automated code reviews on this repo. Configure here.

@decisions-sonarqube

Copy link
Copy Markdown

Quality Gate passed Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant