This is allowed for existing instances so we don't end up 76 offenses
right away, but for new code one should _only_ use this if they _have_
to remove non database data. Even then it's usually better to do this in
a service class as this gives you more control over how to remove the
data (e.g. in bulk).

To make it simpler to assign users to an Issuable, make MergeRequest
support the attribute `assignee_ids`.

Avoid conflicts when merge CE to EE by backporting code from EE.

Instead of checking in `SlashCommands::InterpretService` what the issuable the
type of the issuable is, ask the issuable if it is capable to do those thing and
implement it in the issuable itself. The issuable will check if it's possible
and if the licensed feature is available.

This should also make it easier to ever add multiple assignees to MergeRequests.

Closes #30964

Rémy Coutable authored 8 years ago and DJ Mountney committed 7 years ago

Only show public emails in atom feeds

See merge request !2066

This reverts commit cb10b725c8929b8b4460f89c9d96c773af39ba6b.

Signed-off-by: Rémy Coutable <remy@rymai.me>

Douwe Maan authored 8 years ago and Rémy Coutable committed 8 years ago

Honour issue and merge request visibility in their respective finders

This MR fixes a security issue with the IssuesFinder and MergeRequestFinder where they would return items the user did not have permission to see. This was most visible on the issue and merge requests page for a group containing projects that had set their issues or merge requests to "private".

Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/22481

See merge request !2000

This class can be used to reduce a list of issues down to a subset based
on user permissions. This class operates in such a way that it can
reduce issues using as few queries as possible, if any at all.

fix issues pointed out in !6527

add task completion status feature to CHANGELOG