Jira issues are still visible after disabling "View Jira issues"

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

Summary

If a user has both the View Jira issues and Create Jira issues for vulnerabilities boxes checked on a group, and then the user unchecks only the View Jira issues checkbox and saves, the Jira issues can still be viewed in projects that are inheriting the integration settings.

Steps to reproduce

  1. Create this structure

    > group (public visibility) > project (public visibility)

  2. In the group's settings, configure the Jira issue integration. Ensure that View Jira issues and Create Jira issues for vulnerabilities are enabled. The project should be inheriting the group's integration settings.

  3. Navigate to the project's Jira issues page in a new tab - notice how we can view it

  4. In the group's settings, uncheck the View Jira issues checkbox and save

  5. Go back to the project's Jira issues page - notice how it is still visible even though we have disabled View Jira issues

Example Project

N/A

What is the current bug behavior?

When View Jira issues = false and Create Jira issues for vulnerabilities = true, users can still view the Jira issues for a project.

What is the expected correct behavior?

When View Jira issues = false and Create Jira issues for vulnerabilities = true, users should not be able to view Jira issues.

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)

Possible fixes

Edited by 🤖 GitLab Bot 🤖