1. 25 Feb, 2019 1 commit
  2. 22 Feb, 2019 1 commit
  3. 21 Feb, 2019 2 commits
  4. 05 Feb, 2019 1 commit
  5. 14 Jan, 2019 1 commit
  6. 31 Oct, 2018 1 commit
  7. 26 Oct, 2018 2 commits
  8. 05 Oct, 2018 1 commit
  9. 11 Sep, 2018 2 commits
  10. 06 Jun, 2018 1 commit
    • Sean McGivern's avatar
      Simplify issuable finder queries · 57e6a98c
      Sean McGivern authored
      We had `item_project_ids` to help make slow queries on the dashboard faster, but
      this isn't necessary any more - the queries are plenty fast, and we forbid
      searching the dashboard without filters.
      57e6a98c
  11. 31 May, 2018 1 commit
  12. 21 May, 2018 1 commit
  13. 05 Mar, 2018 1 commit
  14. 21 Feb, 2018 1 commit
    • Sean McGivern's avatar
      Refactor IssuableFinder to extract model-specific logic · c2fc4066
      Sean McGivern authored
      By extracting a new `filter_items` method, we can override that in the
      IssuesFinder and MergeRequestsFinder separately, so we don't need checks that
      the model is the correct one, because we can just use the class we're in to know
      that.
      
      We can do the same for the VALID_PARAMS constant, by making it a class method.
      c2fc4066
  15. 13 Feb, 2018 1 commit
  16. 23 Jan, 2018 1 commit
    • Jan Provaznik's avatar
      Use limit for search count queries · 090ca9c3
      Jan Provaznik authored
      Search query is especially slow if a user searches a generic string
      which matches many records, in such case search can take tens of
      seconds or time out. To speed up the search query, we search only for
      first 1000 records, if there is >1000 matching records we just display
      "1000+" instead of precise total count supposing that with such amount
      the exact count is not so important for the user.
      
      Because for issues even limited search was not fast enough, 2-phase
      approach is used for issues: first we use simpler/faster query to get
      all public issues, if this exceeds the limit, we just return the limit.
      If the amount of matching results is lower than limit, we re-run more
      complex search query (which includes also confidential issues).
      Re-running the complex query should be fast enough in such case because the
      amount of matching issues is lower than limit.
      
      Because exact total_count is now limited, this patch also switches to
      to "prev/next" pagination.
      
      Related #40540
      090ca9c3
  17. 05 Sep, 2017 1 commit
  18. 31 Aug, 2017 1 commit
    • Sean McGivern's avatar
      Remove issuable finder count caching · e7817fc1
      Sean McGivern authored
      We're going to cache the total open count separately, and then just perform
      these counts on the list. We already do that to get the pagination information,
      through Kaminari, and a future change will make Kaminari reuse the query results
      from earlier in the request.
      e7817fc1
  19. 19 Jul, 2017 2 commits
  20. 30 Jun, 2017 6 commits
  21. 23 Jun, 2017 1 commit
    • Toon Claes's avatar
      Add User#full_private_access? to check if user has Private access · b90f1098
      Toon Claes authored
      In CE only the admin has access to all private groups & projects. In EE also an
      auditor can have full private access.
      
      To overcome merge conflicts, or accidental incorrect access rights, abstract
      this out in `User#full_private_access?`.
      
      `User#admin?` now only should be used for admin-only features. For private
      access-related features `User#full_private_access?` should be used.
      
      Backported from gitlab-org/gitlab-ee!2199
      b90f1098
  22. 04 May, 2017 1 commit
  23. 03 Apr, 2017 1 commit
  24. 06 Mar, 2017 1 commit
  25. 17 Feb, 2017 1 commit
  26. 15 Dec, 2016 1 commit
  27. 20 Sep, 2016 1 commit
  28. 18 Mar, 2016 1 commit
  29. 02 Sep, 2014 1 commit
  30. 25 Feb, 2014 1 commit