- 25 Nov, 2017 1 commit
-
-
George Andrinopoulos authored
-
- 07 Nov, 2017 1 commit
-
-
Sean McGivern authored
This method can be called with an array, or a relation: 1. Arrays always have a limited amount of values, so that's fine. 2. If the relation does not have a limit value applied, then we will load every single object in that collection, and prevent N+1 queries for the metadata for that. But that's wrong, because we should never call this without an explicit limit set. So we raise in that case, and this commit will see which specs fail. The only failing specs here were the issues API specs, and the specs for IssuableMetadata itself, and both have been addressed.
-
- 14 Sep, 2017 2 commits
-
-
Jarka Kadlecova authored
-
Jarka Kadlecova authored
-
- 05 Sep, 2017 1 commit
-
-
Hiroyuki Sato authored
-
- 31 Aug, 2017 1 commit
-
-
Robert Schilling authored
-
- 29 Aug, 2017 2 commits
-
-
Travis Miller authored
-
Travis Miller authored
-
- 28 Aug, 2017 2 commits
-
-
Robert Schilling authored
-
Robert Schilling authored
-
- 27 Jul, 2017 1 commit
-
-
Toon Claes authored
Should have been part of !13004.
-
- 25 Jul, 2017 1 commit
-
-
Oswaldo Ferreira authored
-
- 24 Jul, 2017 2 commits
-
-
Toon Claes authored
-
Toon Claes authored
Allow issues filtering on `author_id` and `assignee_id`.
-
- 20 Jul, 2017 1 commit
-
-
Dmitriy Zaporozhets authored
New version of the gem returns 200 status code on delete with content instead of 204 so we explicitly set status code to keep existing behavior Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 06 Jul, 2017 2 commits
-
-
James Lopez authored
-
James Lopez authored
-
- 18 Jun, 2017 1 commit
-
-
Kyle Bishop authored
-
- 04 May, 2017 1 commit
-
-
Valery Sizov authored
-
- 14 Apr, 2017 1 commit
-
-
Sean McGivern authored
CE port of https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/962
-
- 12 Apr, 2017 1 commit
-
-
mhasbini authored
-
- 10 Apr, 2017 1 commit
-
-
Oswaldo Ferreira authored
-
- 05 Apr, 2017 1 commit
-
-
Oswaldo Ferreira authored
Notice that this param is being supported since V3, but we have not added the proper docs for it
-
- 28 Mar, 2017 1 commit
-
-
Alexander Randa authored
-
- 20 Mar, 2017 1 commit
-
-
Adam Niedzielski authored
Closes #29631
-
- 16 Mar, 2017 1 commit
-
-
Rémy Coutable authored
Signed-off-by: Rémy Coutable <remy@rymai.me>
-
- 13 Mar, 2017 3 commits
-
-
Bob Van Landuyt authored
merge_request_for_resolving_discussions -> merge_request_to_resolve_discussions_of
-
Bob Van Landuyt authored
And deduplicate the finding of MR's & discussions. Now the searching is done in the service, istead of the controller & the API.
-
Bob Van Landuyt authored
Delegate a discussion in a merge request into a new issue. The discussion wil be marked as resolved and a system note will be added linking to the newly created issue.
-
- 07 Mar, 2017 1 commit
-
-
Timothy Andrew authored
- As opposed to the issue `id` that was previously being used. - This brings the API routes closer to the web interface's routes. - This is specific to API v4.
-
- 06 Mar, 2017 1 commit
-
-
Adam Niedzielski authored
-
- 01 Mar, 2017 1 commit
-
-
Jarka Kadlecova authored
-
- 23 Feb, 2017 2 commits
-
-
Douwe Maan authored
This reverts commit cb10b725c8929b8b4460f89c9d96c773af39ba6b.
-
Douwe Maan authored
-
- 21 Feb, 2017 1 commit
-
-
Oswaldo Ferreira authored
-
- 20 Feb, 2017 1 commit
-
-
Oswaldo Ferreira authored
-
- 06 Feb, 2017 1 commit
-
-
Oswaldo Ferreira authored
-
- 18 Jan, 2017 1 commit
-
-
Ruben Davila authored
New endpoints are: POST :project_id/(issues|merge_requests)/(:issue_id|:merge_request_id)/time_estimate" POST :project_id/(issues|merge_requests)/(:issue_id|:merge_request_id)/reset_time_estimate" POST :project_id/(issues|merge_requests)/(:issue_id|:merge_request_id)/add_spent_time" POST :project_id/(issues|merge_requests)/(:issue_id|:merge_request_id)/reset_spent_time" GET :project_id/(issues|merge_requests)/(:issue_id|:merge_request_id)/time_stats"
-
- 12 Jan, 2017 2 commits
-
-
David Eisner authored
- Use IssuesFinder for the /issues API resouce - Tests for iid filter in project issues API resource - Tests for No Milestone filter in issues API resources The "No Milestone" case was not previously tested, and the `/issues` resource did not support the the `milestone` parameter. - Return issues where all labels match from the issues and project issues API resources, like the group issues resource already does. See https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/6825#note_17474533Signed-off-by: Rémy Coutable <remy@rymai.me>
-
Panagiotis Atmatzidis authored
Current filtering for "/projects/:id/issues" endpoint returns no results for "No Milestone" query. This PR introduces fix by copying filtering from "/groups/:id/issues" which works as expected.
-