Deployed-After filter for merge requests displays no results
Summary
The Deployed-After filter for Merge Requests is showing no results in a particular instance, but seems to be meeting the criteria for the filter.
In this particular project, there are over 500+ merged MRs. With the below, we can see an example MR. The docs state:
the date refers to when the deployment to an environment (triggered by the merge commit) completed successfully.
- This example MR was deployed to an environment after the configured date
- It was triggered via a merge commit
- The deployment was successful
Deploy dates use the format YYYY-MM-DD
- Format is correct
- Making changes to the format or trying different formats produced the same results. Having a date picker would help to confirm the format since MM-DD-YYYY can be accepted.
Using the API https://gitlab.com/api/v4/projects/:project_id/merge_requests?state=merged&deployed_after=2022-01-01T08:00:00Zon this project produces no results as well, but if you do this on gitlab-org/gitlab it appears to return results fine:
I am seeing no discernible difference between this project and others. It's unclear if we are not accounting for a specific scenario that is not documented, or if we are encountering a bug in this project.
Steps to reproduce
It only seems reproducible in a specific project, as other projects are not showing this behavior.
Example Project
See ZD Ticket
What is the current bug behavior?
Filtering merge requests with Deployed-After produces no results.
What is the expected correct behavior?
Filtering merge requests with Deployed-After should filter MRs that have been deployed to environments successfully.
Relevant logs and/or screenshots
Output of checks
GitLab.com 14.10.0-pre c0e71648
Results of GitLab environment info
Expand for output related to GitLab environment info
(For installations with omnibus-gitlab package run and paste the output of: `sudo gitlab-rake gitlab:env:info`) (For installations from source run and paste the output of: `sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)
Results of GitLab application Check
Expand for output related to the GitLab application check
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true)(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true)(we will only investigate if the tests are passing)