gitlabhq

mirror of https://github.com/wahyd4/gitlabhq.git synced 2026-08-12 06:06:05 +10:00

Files

T

Douwe Maan 0c0ef7dfb6 Merge branch 'confidential-issues-in-private-projects' into 'master'

Allow users to create confidential issues in private projects

Closes #14787

## What does this MR do?

Allow users to create confidential issues in private projects, and exclude access to them to project members with `Guest` role.

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

The query generated by the `User#authorized_projects` method.

## Why was this MR needed?

Community have been requesting this feature.

## What are the relevant issue numbers?

https://gitlab.com/gitlab-org/gitlab-ce/issues/14787

https://gitlab.com/gitlab-org/gitlab-ce/issues/3678

## Screenshots (if relevant)

Not relevant.

## Todo

- [x] Allow users to create confidential issues in private projects
- [x] Project members with `Guest` role should not have access to confidential issues
- [ ] ~~Apply changes in EE + Elasticsearch~~ Will be done in another MR, when this got merged

See merge request !3471

2016-06-14 09:35:18 +00:00

config

Enable the Rubocop DeprecatedClassMethods cop

2016-05-08 15:33:34 -06:00

controllers

Project members with guest role can't access confidential issues

2016-06-13 19:32:00 -03:00

factories

Remove deprecated issues_tracker and issues_tracker_id from project

2016-06-13 18:13:55 -03:00

features

Apply reviewer notes: update CHANGELOG, adjust code formatting