<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=582609) </details> <!--IssueSummary end--> ## What is this about? As discussed in https://gitlab.com/gitlab-org/gitlab/-/merge_requests/213476#note_2922888597, `deployed_after` and `deployed_before` params should have `type: DateTime` to handle param validations, but it would fail currently if we add types now due to the [custom parsing logic](https://gitlab.com/gitlab-org/gitlab/-/blob/48965ceda66201126327c60c99df9188b227e5d8/app/finders/merge_requests_finder.rb#L357) ## Potential Fixes - Set `type: DateTime` to those params and return early if the param is already DateTime - Confirm if the custom parsing logic is still required. If not, we should just be able to set `type: DateTime` once the custom logic is removed. ## Related to - https://gitlab.com/gitlab-org/gitlab/-/merge_requests/213476#note_2925016814