BigW Consortium Gitlab

  1. 19 Oct, 2016 4 commits
  2. 30 Sep, 2016 1 commit
  3. 20 Sep, 2016 1 commit
  4. 30 Aug, 2016 1 commit
  5. 01 Aug, 2016 1 commit
    • State specific default sort order for issuables · 84a3225b
      zs authored
      Provide more sensible default sort order for issues and merge requests
      based on the following table:
      
      | type           | state  | default sort order |
      |----------------|--------|--------------------|
      | issues         | open   | last created       |
      | issues         | closed | last updated       |
      | issues         | all    | last created       |
      | merge requests | open   | last created       |
      | merge requests | merged | last updated       |
      | merge requests | closed | last updated       |
      | merge requests | all    | last created       |
  6. 06 Jun, 2016 2 commits
  7. 03 Jun, 2016 2 commits
  8. 31 May, 2016 1 commit
  9. 24 May, 2016 2 commits
  10. 16 May, 2016 1 commit
    • Make upcoming milestone work across projects · 750b2ff0
      Sean McGivern authored
      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).
  11. 21 Apr, 2016 1 commit
  12. 20 Apr, 2016 7 commits
  13. 19 Apr, 2016 1 commit
  14. 13 Apr, 2016 1 commit
  15. 29 Mar, 2016 2 commits
  16. 21 Mar, 2016 1 commit
  17. 20 Mar, 2016 2 commits
  18. 13 Mar, 2016 1 commit
  19. 12 Mar, 2016 3 commits
  20. 07 Mar, 2016 1 commit
  21. 19 Feb, 2016 2 commits
  22. 18 Jan, 2016 1 commit
    • Scope issue projects to a Group when possible · d6a8021e
      Yorick Peterse authored
      When using IssuableFinder with a Group we can greatly reduce the amount
      of projects operated on (due to not including all public/internal
      projects) by simply passing it down to the ProjectsFinder class.
      
      This reduces the timings of the involved queries from roughly 300
      ms to roughly 20 ms.
      
      Fixes gitlab-org/gitlab-ce#4071, gitlab-org/gitlab-ce#3707
  23. 07 Jan, 2016 1 commit
    • Drop projects order in IssuableFinder · fc443ea7
      Yorick Peterse authored
      When grabbing the projects to filter issues by we don't care about the
      order they're returned in. By removing the ORDER BY the resulting query
      can be quite a bit faster.