1. 23 Feb, 2017 1 commit
  2. 17 Feb, 2017 1 commit
  3. 11 Jan, 2017 1 commit
  4. 09 Jan, 2017 4 commits
  5. 09 Dec, 2016 1 commit
  6. 06 Dec, 2016 1 commit
  7. 05 Dec, 2016 1 commit
    • Jacopo's avatar
      Fix Archived project merge requests add to group's Merge Requests · dcfc8b9a6dfb
      Jacopo authored
      counter
      
      This is done by:
       - Extending the IssuableFinder adding the non_archived option to the params
       - Overriding the #filter_params in the MergeRequestsAction
       - Passing the non_archived param in the nav/_group.html.haml navbar
         partial from the groups/merge_requests.html.haml
      dcfc8b9a6dfb
  8. 01 Dec, 2016 1 commit
    • Sean McGivern's avatar
      Count all issuable states at once · 325f385148b9
      Sean McGivern authored
      Instead of doing n queries for n states, do one query to get all the
      counts grouped by state, and figure out what the count is for each state
      is from that. We can still cache the individual counts (it can't hurt),
      but this will help with initial load.
      
      Note that the `opened` scope on `Issuable` includes the `opened` and
      `reopened` states, which is why there's a special case.
      325f385148b9
  9. 29 Nov, 2016 2 commits
  10. 26 Nov, 2016 1 commit
  11. 09 Nov, 2016 1 commit
  12. 01 Nov, 2016 1 commit
  13. 19 Oct, 2016 4 commits
  14. 30 Sep, 2016 1 commit
  15. 20 Sep, 2016 1 commit
  16. 30 Aug, 2016 1 commit
  17. 01 Aug, 2016 1 commit
    • zs's avatar
      State specific default sort order for issuables · cb4c5d66724c
      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       |
      cb4c5d66724c
  18. 06 Jun, 2016 2 commits
  19. 03 Jun, 2016 2 commits
  20. 31 May, 2016 1 commit
  21. 24 May, 2016 2 commits
  22. 16 May, 2016 1 commit
    • Sean McGivern's avatar
      Make upcoming milestone work across projects · 6dcb77744929
      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).
      6dcb77744929
  23. 21 Apr, 2016 1 commit
  24. 20 Apr, 2016 7 commits