Read about our upcoming Code of Conduct on this issue

  1. 21 Aug, 2019 1 commit
    • George Koltsov's avatar
      Add SortingPreference concern · 3c45523d4c1c
      George Koltsov authored
      Sorting preference functionality has been extracted
      from `IssuableCollections` to a new `SortingPreference`
      concern in order to reuse this functionality in projects
      (and groups in the future).
  2. 31 Jul, 2019 1 commit
  3. 16 Jul, 2019 1 commit
  4. 09 Jul, 2019 1 commit
    • charlie ablett's avatar
      Remove `:graphql` feature flag · 67df73f54346
      charlie ablett authored
      - Remove `FeatureConstrainer` call wrapping api endpoint
      - Remove `Feature.enabled?(:graphql)` conditionals in back and frontend
      - Modify graphql test to be graphql flag agnostic
      - Remove api routing spec
      - Remove frontend feature flag via `gon`
  5. 05 Jul, 2019 1 commit
  6. 28 Jun, 2019 1 commit
  7. 26 Jun, 2019 1 commit
    • Rajat Jain's avatar
      Bring Manual Ordering on Issue List · 201abea36d7c
      Rajat Jain authored
      On all the issue lists -- Group, Project and Dashboard -- this
      change adds a new option for managing the lists.
      "Manual Ordering" option is added which when flipped on will allow
      an user to drag and drop issues around to create a relative ordering
      among them.
  8. 21 Jun, 2019 1 commit
  9. 18 Apr, 2019 1 commit
  10. 15 Apr, 2019 1 commit
    • Fatih Acet's avatar
      Delete leftover code for referenced_merge_requests · cc205404db37
      Fatih Acet authored
      We rewrote Related MRs widget using Vue.
      The previous implementation was using Haml templates
      and calling referenced_merge_requests endpoint which is
      now deprecated. This MR deletes leftover stuff them.
  11. 27 Mar, 2019 1 commit
  12. 21 Mar, 2019 1 commit
  13. 05 Feb, 2019 2 commits
  14. 31 Jan, 2019 1 commit
  15. 30 Jan, 2019 2 commits
  16. 28 Jan, 2019 1 commit
    • Mario de la Ossa's avatar
      Save sorting preference for Issues/MRs in BE · 7df1020f4fa6
      Mario de la Ossa authored
      In order to let users' sorting preferences transfer between devices, we
      save the preference for issues and MRs (one preference for issues, one
      for MRs) in the backend inside the UserPreference object
  17. 14 Jan, 2019 1 commit
  18. 11 Jan, 2019 1 commit
  19. 07 Jan, 2019 3 commits
  20. 13 Dec, 2018 1 commit
  21. 29 Nov, 2018 1 commit
  22. 27 Nov, 2018 1 commit
    • Phil Hughes's avatar
      Suggests issues when typing title · 746ef465ad49
      Phil Hughes authored
      This suggests possibly related issues when the user types a title.
      This uses GraphQL to allow the frontend to request the exact
      data that is requires. We also get free caching through the Vue Apollo
      With this we can include the ability to import .graphql files in JS
      and Vue files.
      Also we now have the Vue test utils library to make testing
      Vue components easier.
      Closes #22071
  23. 23 Nov, 2018 1 commit
  24. 24 Oct, 2018 1 commit
  25. 04 Oct, 2018 1 commit
  26. 26 Sep, 2018 1 commit
    • gfyoung's avatar
      Enable even more frozen string in app/controllers · 73f4d7f633c9
      gfyoung authored
      Enables frozen string for some vestigial files as
      well as the following:
      * app/controllers/projects/**/*.rb
      * app/controllers/sherlock/**/*.rb
      * app/controllers/snippets/**/*.rb
      * app/controllers/users/**/*.rb
      Partially addresses #47424.
  27. 11 Sep, 2018 1 commit
  28. 21 Aug, 2018 1 commit
    • Sean McGivern's avatar
      Move Issue#{referenced,closed_by}_merge_requests to service · 8f97142bd7a9
      Sean McGivern authored
      These methods don't really need to be on the Issue model. Issue#related_branches
      can also be moved to a service, but we can do that in a separate commit.
      This commit does not change any behaviour; it just moves code around, renames
      the service, and refactors the specs.
  29. 30 Jul, 2018 1 commit
    • Bob Van Landuyt's avatar
      Show the status of a user in interactions · a4d26a719e14
      Bob Van Landuyt authored
      The status is shown for
      - The author of a commit when viewing a commit
      - Notes on a commit (regular/diff)
      - The user that triggered a pipeline when viewing a pipeline
      - The author of a merge request when viewing a merge request
      - The author of notes on a merge request (regular/diff)
      - The author of an issue when viewing an issue
      - The author of notes on an issue
      - The author of a snippet when viewing a snippet
      - The author of notes on a snippet
      - A user's profile page
      - The list of members of a group/user
  30. 18 Jun, 2018 1 commit
    • Imre Farkas's avatar
      Render calendar feed inline when accessed from GitLab · 61fb2273f342
      Imre Farkas authored
      With text/calendar as Content-Type, the browser always downloads the
      content as a file (even ignoring the Content-Disposition header). We
      want to display the content inline when accessed from GitLab, similarly
      to the RSS feed.
  31. 31 May, 2018 1 commit
  32. 19 Apr, 2018 1 commit
  33. 11 Apr, 2018 2 commits
    • Bob Van Landuyt's avatar
      Correct permissions for creating merge requests from issues · cda254ad99ec
      Bob Van Landuyt authored
      This could only be possible for users that can create merge requests
      within a project.
      So they need to be a allowed to create a branch and create a merge request.
    • Bob Van Landuyt's avatar
      Rename `create_merge_request` permissions · ccfe22c2e838
      Bob Van Landuyt authored
      So we can distinguish between the permissions on the source and the
      target project.
      - `create_merge_request_from` indicates a user can create a merge
        request with the project as a source_project
      - `create_merge_request_in` indicates a user can create a merge
        request with the project as a target_project
  34. 28 Feb, 2018 1 commit
  35. 21 Feb, 2018 1 commit
    • Sean McGivern's avatar
      Refactor IssuableFinder to extract model-specific logic · 8bd617d3949f
      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
      We can do the same for the VALID_PARAMS constant, by making it a class method.