delta/gitlab/gitlab-ce.git/doc/api/issues.md, branch fix-include-description-commit-message gitlab.com: gitlab-org/gitlab-ce.git Merge branch 'time-tracking-api' into 'master' 2017-01-19T09:58:48+00:00 Sean McGivern sean@mcgivern.me.uk 2017-01-18T18:18:13+00:00 86e46688d794a58559ccefc0a0bc8a8d57401dcd Time tracking API Closes #25861 See merge request !8483 

Time tracking API

Closes #25861

See merge request !8483
 API: Implement project issues iid param with IssuesFinder and add tests 2017-01-12T22:51:06+00:00 David Eisner david.eisner@oriel.oxon.org 2016-10-26T08:08:58+00:00 7ef1c6408e95c780e947e5c56cfae10b3dbb03d4 - 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_17474533 Signed-off-by: Rémy Coutable <remy@rymai.me> 
- 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_17474533

Signed-off-by: Rémy Coutable <remy@rymai.me>
Feature: delegate all open discussions to Issue 2016-12-05T19:55:45+00:00 Bob Van Landuyt bob@vanlanduyt.co 2016-10-26T21:21:50+00:00 1123057ab792ac73b1611f4d3a9faf79369dd6da When a merge request can only be merged when all discussions are resolved. This feature allows to easily delegate those discussions to a new issue, while marking them as resolved in the merge request. The user is presented with a new issue, prepared with mentions of all unresolved discussions, including the first unresolved note of the discussion, time and link to the note. When the issue is created, the discussions in the merge request will get a system note directing the user to the newly created issue. 
When a merge request can only be merged when all discussions are
resolved. This feature allows to easily delegate those discussions to a
new issue, while marking them as resolved in the merge request.

The user is presented with a new issue, prepared with mentions of all
unresolved discussions, including the first unresolved note of the
discussion, time and link to the note.

When the issue is created, the discussions in the merge request will get
a system note directing the user to the newly created issue.
Remove unnecessary sentences for status codes in the API documentation 2016-11-24T17:28:52+00:00 Luis Alonso Chavez Armendariz lchavez@nearsoft.com 2016-11-24T17:28:52+00:00 ed61d44e1edfd41c36ec9085aa95f470bb5699fa 






Remove /u/ prefix from user pages in documentation
2016-10-13T11:24:09+00:00

Dmitriy Zaporozhets
dmitriy.zaporozhets@gmail.com

2016-10-13T11:24:09+00:00

cb7872c3a0c789f9e906492098bb7d643f135e52

Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>





Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>







API: Expose issue#confidential
2016-08-31T07:20:04+00:00

Robert Schilling
rschilling@student.tugraz.at

2016-07-15T14:21:53+00:00

036cc8c27e8340a3eed63444bd3f42f86037f350












Merge branch 'entity-api-web-url' into 'master'

2016-08-24T19:26:04+00:00

Douwe Maan
douwe@gitlab.com

2016-08-24T19:26:04+00:00

90441e85ddb0b24550521c458fe12baf65e5352c


api: expose web_url for project entities

## What does this MR do?

Adds a `web_url` field to project snippet, issues, and merge request API returned objects.

## Are there points in the code the reviewer needs to double check?

Tests. Are they sufficient? (I'm working on getting them to pass.)

## Why was this MR needed?

Creating the URL for an MR or issue from the MR is tedious in API libraries; it's easy for Gitlab to just provide it.

## What are the relevant issue numbers?

N/A

## Screenshots (if relevant)

N/A

## Does this MR meet the acceptance criteria?

- [x] [CHANGELOG](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CHANGELOG) entry added
- [x] [Documentation created/updated](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/development/doc_styleguide.md)
- [x] API support added
- Tests
  - [x] Added for this feature/bug
  - [x] All builds are passing
- [x] Conform by the [style guides](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CONTRIBUTING.md#style-guides)
- [x] Branch has no merge conflicts with `master` (if you do - rebase it please)
- [x] [Squashed related commits together](https://git-scm.com/book/en/Git-Tools-Rewriting-History#Squashing-Commits)

See merge request !5631





api: expose web_url for project entities

## What does this MR do?

Adds a `web_url` field to project snippet, issues, and merge request API returned objects.

## Are there points in the code the reviewer needs to double check?

Tests. Are they sufficient? (I'm working on getting them to pass.)

## Why was this MR needed?

Creating the URL for an MR or issue from the MR is tedious in API libraries; it's easy for Gitlab to just provide it.

## What are the relevant issue numbers?

N/A

## Screenshots (if relevant)

N/A

## Does this MR meet the acceptance criteria?

- [x] [CHANGELOG](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CHANGELOG) entry added
- [x] [Documentation created/updated](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/development/doc_styleguide.md)
- [x] API support added
- Tests
  - [x] Added for this feature/bug
  - [x] All builds are passing
- [x] Conform by the [style guides](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CONTRIBUTING.md#style-guides)
- [x] Branch has no merge conflicts with `master` (if you do - rebase it please)
- [x] [Squashed related commits together](https://git-scm.com/book/en/Git-Tools-Rewriting-History#Squashing-Commits)

See merge request !5631






api: expose web_url for project entities
2016-08-24T14:32:31+00:00

Ben Boeckel
ben.boeckel@kitware.com

2016-08-02T17:37:04+00:00

e43c4060b67c1996b917bc00afa72122d1d00004

This allows web hooks to have a URL back to entities without having to
generate it themselves.





This allows web hooks to have a URL back to entities without having to
generate it themselves.







docs: fix table alignment
2016-08-24T14:29:58+00:00

Ben Boeckel
ben.boeckel@kitware.com

2016-08-23T17:57:34+00:00

a5f3bdc5c862944f755f1e61bf965a54e0a6d95d












docs: update created_at docs for creating issues via API
2016-08-24T14:29:41+00:00

Ben Boeckel
ben.boeckel@kitware.com

2016-08-23T17:56:21+00:00

ae4efc8d5e6a195452f0ecf550198575c63a49b9

See also #19863.

Fixes #18458.





See also #19863.

Fixes #18458.