750b2ff0ee
Before: we took the next milestone due across all projects in the search and found issues whose milestone title matched that one. Problems: 1. The milestone could be closed. 2. Different projects have milestones with different schedules. 3. Different projects have milestones with different titles. 4. Different projects can have milestones with different schedules, but the _same_ title. That means we could show issues from a past milestone, or one that's far in the future. After: gather the ID of the next milestone on each project we're looking at, and find issues with those milestone IDs. Problems: 1. For a lot of projects, this can return a lot of IDs. 2. The SQL query has to be different between Postgres and MySQL, because MySQL is much more lenient with HAVING: as well as the columns appearing in GROUP BY or in aggregate clauses, MySQL allows them to appear in the SELECT list (un-aggregated). |
||
|---|---|---|
| .. | ||
| contributed_projects_finder_spec.rb | ||
| group_projects_finder_spec.rb | ||
| groups_finder_spec.rb | ||
| issues_finder_spec.rb | ||
| joined_groups_finder_spec.rb | ||
| merge_requests_finder_spec.rb | ||
| notes_finder_spec.rb | ||
| personal_projects_finder_spec.rb | ||
| projects_finder_spec.rb | ||
| snippets_finder_spec.rb | ||
| trending_projects_finder_spec.rb | ||