Issue Summary

First of all, the next-gen projects don't have a permission scheme. So, if we restrict the permission View development tools on a classic software project for a specific group, even a user not belonging to that group, the user will be able to see the development field on an issue from a next-gen software project.

Steps to Reproduce

1. Enable the development tools integration on a project
2. Edit the permission view development tools on the permission scheme of this project for a specific group.
3. Choose a user and to ensure that it's not nested on that group
4. Access a next-gen project and see an issue

Expected Results

https://share.getcloudapp.com/E0unlDJX

Actual Results

https://share.getcloudapp.com/KourLv8W

Workaround

Currently, there is no known workaround for this behavior. A workaround will be added here when available.