summaryrefslogtreecommitdiff
path: root/CHANGELOG
diff options
context:
space:
mode:
authorDouwe Maan <douwe@gitlab.com>2016-06-14 09:35:18 +0000
committerDouwe Maan <douwe@gitlab.com>2016-06-14 09:35:18 +0000
commit0c0ef7dfb6afb1695b62037fc0fa5aba6ce697d7 (patch)
tree001a653dc38b6bf6ed52b5d59b53e8525f894a4c /CHANGELOG
parent0068ba8db597a0396ce1eddd51776981dd12d970 (diff)
parent6789d2ebf37d5f0537bea72ba99d3b7711e70728 (diff)
downloadgitlab-ce-0c0ef7dfb6afb1695b62037fc0fa5aba6ce697d7.tar.gz
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
Diffstat (limited to 'CHANGELOG')
-rw-r--r--CHANGELOG1
1 files changed, 1 insertions, 0 deletions
diff --git a/CHANGELOG b/CHANGELOG
index 70dd9dd70e1..2aed8eb322b 100644
--- a/CHANGELOG
+++ b/CHANGELOG
@@ -76,6 +76,7 @@ v 8.9.0 (unreleased)
- Put project Labels and Milestones pages links under Issues and Merge Requests tabs as subnav
- All classes in the Banzai::ReferenceParser namespace are now instrumented
- Remove deprecated issues_tracker and issues_tracker_id from project model
+ - Allow users to create confidential issues in private projects
v 8.8.5 (unreleased)
- Ensure branch cleanup regardless of whether the GitHub import process succeeds