...
Note, that if you omit assigning the other actions to the relevant Project Role, Application Access or Group then the relevant Jira Users will not be able to manage the created Problems or Possibilities.
...
Step #3 - Create & modify a Field Configuration to make "Reporter" optional
...
Alternatively, you could change the field configuration already applied to the project you want to make public.
...
Step #4 - Create a Field Configuration Scheme
...
Navigate to the "Field Configuration Scheme" page through the Jira main menu (Jira Settings > Issues > Field Configurations Schemes)
Click "Add field configuration scheme", name it something appropriate (e.g. "Public Access Field Configuration Scheme")
Under the "Actions" column click "Configure" for the newly created configuration scheme
Associate Problem and Possibility issue types with the newly created field configuration scheme
Add any other issues types you'd like anonymous users to be able to create (e.g. task), otherwise they will receive a "reporter required" error
...
Step #5 - Apply the public permission scheme and field configuration
...
Navigate to Settings for the project you would like to have publicly accessible
Select a different permission scheme for your chosen project (Permissions > Actions > Use a different scheme)
From the drop-down list, select the public access permission scheme create in Step #1 and click "Associate"
Select a different field configuration (Fields > Actions > Use a different scheme)
From the drop-down list, select the public access field configuration scheme created in Step #4 and click "Associate"
...
Step #6 - Test public access
...
Navigate to your project URL that you applied the public schemes (e.g. https://tryble.atlassian.net/projects/PUB/board)
From the Board or "+" on the global menu try to create a Problem or Possibility
...
For additional information, please consult Atlassian documentation:
| Info |
|---|