Issue Summary

While using Jira Issue/Filter Macro - Create New Issue, the Project Drop Down enlist all the projects even if the user is not having permission to "Create Issue" for a particular Project. The Project Drop Down Menu should only list projects for which the User has permissions to create issues.

The reason for this bug request is currently if there are lot of Jira Projects its difficult for the users to identify which project he/she is having permission. Only after clicking on the particular Project the user is able to know that the user is not having permission to create issue. Ideally the User should be only rendered with only those Projects in Drop Down for which the User is having permission of "Create Issue" in Jira.

This is reproducible on Data Center: (yes) / (no) Yes

Steps to Reproduce

1. Create any project with permission of "Browse Projects" with all/any logged in user
2. Checkout the project is having permission "Create Issues" for only admin/group of users. Below example is where projects CHR and mark are not having permissions for "Create Issue" for any other user apart from admin.
   
3. Login Confluence with some other user which is not having "Create Issues" Permission(refer step2) and Create a page
4. User Jira Issue/Filter Macro in the page and navigate to "Create New Issue"
5. Under Project Menu -> Select a Project - This will show the project in the drop down list which we create in step 1/2. Below is the screenshot where this user though not having permission to create issue is been enlisted with projects "CHR" and "mark". These 2 projects shouldn't be there in the drop down menu for Project list
   
6. This project should not be visible to the user in Confluence if the User is not having permission to create issue in that particular Project.

Expected Results

The User should only be rendered with the list of Jira Projects for which the user is having permission for "Create Issue" for a project.

Actual Results

The User is been rendered with list of all the Jira Projects in "Create New Issue" menu irrespective of "Create Issue" Permissions provided for the user.

Workaround

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