delta/gitlab/gitlab-ce.git/app/services/issues, branch diff-notes-refactor

delta/gitlab/gitlab-ce.git/app/services/issues, branch diff-notes-refactor gitlab.com: gitlab-org/gitlab-ce.git Use reCaptcha when an issue identified as spam 2017-02-07T11:56:20+00:00 Jarka Kadlecova jarka@gitlab.com 2017-01-27T16:25:39+00:00 3d2954e4570d236a080b0d46698d96a28fd9acec

Check if user can read issue before being assigned 2016-12-27T21:25:17+00:00 Felipe Artur felipefac@gmail.com 2016-12-14T21:39:53+00:00 1b082a4c338d7575e15d7450906801db59873441

Enable Style/MultilineOperationIndentation in Rubocop, fixes #25741 2016-12-16T18:37:22+00:00 Rydkin Maxim maks.rydkin@gmail.com 2016-12-15T22:14:20+00:00 170efaaba273792ddffc2806ef1501f33d87a5a2

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.

Refactor JiraService by moving code out of JiraService#execute method 2016-12-01T08:45:06+00:00 Adam Niedzielski adamsunday@gmail.com 2016-12-01T08:45:06+00:00 1105597303496e60308f93441b591a6f7dfadc74 The implicit interface of project services states that the "execute" method is meant to be called when project hooks are executed. Currently JiraService does not support any project events even though JiraService#supported_events says that "commit" and "merge_request" are supported. They are only used to render correct options in JIRA configuration screen, but they are not supported. Because of that, this commit makes "execute" method a no-op.

The implicit interface of project services states that the "execute"
method is meant to be called when project hooks are executed.
Currently JiraService does not support any project events even though
JiraService#supported_events says that "commit" and "merge_request"
are supported. They are only used to render correct options in
JIRA configuration screen, but they are not supported.
Because of that, this commit makes "execute" method a no-op.

Process commits in a separate worker 2016-11-07T12:11:44+00:00 Yorick Peterse yorickpeterse@gmail.com 2016-10-07T13:20:57+00:00 509910b89f636f95d2d5a9cd3f38ce8f7f4f47a6 This moves the code used for processing commits from GitPushService to its own Sidekiq worker: ProcessCommitWorker. Using a Sidekiq worker allows us to process multiple commits in parallel. This in turn will lead to issues being closed faster and cross references being created faster. Furthermore by isolating this code into a separate class it's easier to test and maintain the code. The new worker also ensures it can efficiently check which issues can be closed, without having to run numerous SQL queries for every issue.

This moves the code used for processing commits from GitPushService to
its own Sidekiq worker: ProcessCommitWorker.

Using a Sidekiq worker allows us to process multiple commits in
parallel. This in turn will lead to issues being closed faster and cross
references being created faster. Furthermore by isolating this code into
a separate class it's easier to test and maintain the code.

The new worker also ensures it can efficiently check which issues can be
closed, without having to run numerous SQL queries for every issue.

Include global labels when moving an issue to another project 2016-10-19T16:58:25+00:00 Douglas Barbosa Alexandre dbalexandre@gmail.com 2016-09-28T19:17:41+00:00 484f19ed1c5c07cbf8ea26fab8b6759961fcf9ca

Add bulk update support for merge requests list 2016-09-08T08:52:20+00:00 Dmitriy Zaporozhets dmitriy.zaporozhets@gmail.com 2016-09-06T12:49:49+00:00 f28ca293b78405d798f1df78a39d549157a57c07 Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>

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

Scope hooks thal will run for confidential issues 2016-08-31T21:34:45+00:00 Douglas Barbosa Alexandre dbalexandre@gmail.com 2016-08-30T22:11:46+00:00 21f10af0956c69b6a5bad6b36b7d6e12e60e7867

Fix confidential issues should not be passed to Webhooks 2016-08-31T21:33:14+00:00 Douglas Barbosa Alexandre dbalexandre@gmail.com 2016-08-12T19:05:10+00:00 44340fede26278a7f9d70e0fb063df9673cfc551