BigW Consortium Gitlab

  1. 09 Nov, 2016 1 commit
  2. 01 Nov, 2016 1 commit
  3. 19 Oct, 2016 4 commits
  4. 30 Sep, 2016 1 commit
  5. 20 Sep, 2016 1 commit
  6. 30 Aug, 2016 1 commit
  7. 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       |
  8. 06 Jun, 2016 2 commits
  9. 03 Jun, 2016 2 commits
  10. 31 May, 2016 1 commit
  11. 24 May, 2016 2 commits
  12. 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).
  13. 21 Apr, 2016 1 commit
  14. 20 Apr, 2016 7 commits
  15. 19 Apr, 2016 1 commit
  16. 13 Apr, 2016 1 commit
  17. 29 Mar, 2016 2 commits
  18. 21 Mar, 2016 1 commit
  19. 20 Mar, 2016 2 commits
  20. 13 Mar, 2016 1 commit
  21. 12 Mar, 2016 3 commits
  22. 07 Mar, 2016 1 commit
  23. 19 Feb, 2016 2 commits