Issue Summary

This bug is related to custom project roles on team-managed projects.
Whenever we create a new project role, if we associate the create issue permission to that custom role, it also allows the user to edit issues after the project creation.

Steps to Reproduce

1. Create a team-managed project.
2. Create a custom role.
3. Associate the project permission "create issue" to that custom project role.
4. Associate a user to that role and make sure that the user does not have any other project permission except for the "create issue" granted by the custom project role.
5. Impersonate the user.
6. Create a new issue inside the project that we created in step 1.
7. Open the issue, you will be able to edit it, even without the project permission Edit issue.

Expected Results

Based on the description that we have for the project issue Create issue, it should allow the user to create a new issue, but not to edit that issue after its creation.

Actual Results

The project permission Create issue is also allowing the user to edit the project issues.

Workaround

None