Epics - adding new child issue dropdown does not show projects that are shared with the group
Summary
When adding a new issue to an epic, the project dropdown list does not show projects that were shared with the group.
Steps to reproduce
- Create 2 top level groups
alpha
andbeta
- Within the
beta
group, create a project - Ensure that the prevent a project from being shared with groups is unchecked on the
beta
group - Share the project in step 2 with
alpha
(as per share a project with a group) - Create an epic within the
alpha
group - Within the epic, attempt to adding a new issue to an epic and activate the project dropdown.
Example Project
N/A
What is the current bug behavior?
The project dropdown in the new child issue dropdown for epics does not show projects that are shared with the group.
What is the expected correct behavior?
The project dropdown in the new child issue dropdown for epics should show projects that are shared with the group.
Relevant logs and/or screenshots
Output of checks
Results of GitLab environment info
Expand for output related to GitLab environment info
(For installations with omnibus-gitlab package run and paste the output of: `sudo gitlab-rake gitlab:env:info`) (For installations from source run and paste the output of: `sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)
Results of GitLab application Check
Expand for output related to the GitLab application check
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true
)(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true
)(we will only investigate if the tests are passing)
Workarounds
- Use the add an existing issue to an epic workflow instead
Possible fixes
The project dropdown is populated via an XHR request api/v4/groups/<GROUP_ID>/projects?include_subgroups=true&order_by=last_activity_at&with_issues_enabled=true&search_namespaces=true&with_shared=false
.
Changing with_shared=false
to with_shared=true
might be all that's needed here?