Allow anonymous issue creation but prevent anonymous viewing of issues in Jira
プラットフォームについて: Cloud および Data Center - この記事はクラウドと Data Center 両方のプラットフォームに等しく適用されます。
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Fisheye および Crucible は除く
目的
This KB instructs on how to allow the creation of issues anonymously while preventing the user from seeing issues in JIRA Core Server and Jira Work Management Cloud. Alternatively, issues can be opened to anonymous users by Configuring issue-level security as per that documentation. A sample use case of this is to allow production bug reports to be anonymously submitted and kept private from viewing.
To allow anonymous users to create and browse all issues in the project without restricting their view, follow our How to Enable Anonymous Issue Submission FAQ.
Note: Anonymous reporters will not receive notifications of issue updates because no user will be linked to the Reporter field of the issue.
ソリューション
- Edit the permission scheme for your desired project as per Managing project permissions to give the group 'Anyone' permission to Browse Projects and Create Issues.
- If you want the users to be able to add attachments, give the group 'Anyone' permission to Create Attachments as well
- It's not possible to add attachments when creating an issue anonymously via REST API. It can't be done in a single API request (the following Suggestion has been raised for this: JRASERVER-70074 - As a user, I want to be able to create an issue with an attachment via the REST API and JRACLOUD-77434 - As a user, I want to be able to create an issue with an attachment via the REST API) and also not possible in multiple API requests because anonymous users have no access to the issue once it has been created.
- Give the project role 'Administrators' permission to Set Issue Security.
- Create an Issue-Level Security Scheme and add a security level to that issue that permits access to only the 'Users' group.
- Set that permission level as default, so any new issue created will only be visible to members of the group Users.
- Assign your new Issue Level Security Scheme to the project mentioned in step one.
- Search for all issues in the project mentioned in step one, hit tools->bulk change all x issues, click edit, and change the security level to the one created in step 2.
Now any existing issues won't be visible to anonymous users but can be made visible by Configuring issue-level security.