Create a private Jira project only specific users can access
プラットフォームについて: Cloud のみ - この記事は クラウド プラットフォームのアトラシアン製品に適用されます。
要約
If you require a Jira project with limited or private access, you can create one that will only be visible to the users you specify.
Common use cases for a private Jira project
By default, Jira Administrators have access to newly created Projects. When handling sensitive information or work related to Human Resources, medical information, or any other type of data, you may wish to create a project that even Jira admins or site-admins cannot access.
Which Jira project types can I configure to be completely private?
The steps in this article are compatible with both Team-managed and Company-managed projects.
You can follow these steps for Software and Work management project types, both Team-managed and Company-managed.
Preparation steps
- Create a new Jira project with no issue data included in it
- Create a group or project role to be associated with the users that should be able to view this project's data
- Create a group or project role to be assigned to the project Administrator(s) that will maintain the project moving forward
- Add yourself to the chosen group and/or project role from steps 2 and 3 to allow yourself to fully configure the project
- Add any of the relevant users or project administrators to their respective group or project role
- This step can be performed later, but will need to be performed before you remove your own access to keep the project's data private
The group names and project role names that you choose here will be publicly visible to Jira and site administrators.
Configure the project to be private
The steps differ depending on which project type you've chosen.
For a Team-Managed project:
- Go to Project Settings
- Select the Access option
- Select Change Project Access
- Set the project Access to Private then click the Change button
For a Company-Managed project
Company-managed projects utilize Permission Schemes, which are built to allow for sharing permissions between multiple Jira projects.
If our private project uses a scheme that is shared with other projects, any changes we make to this scheme will affect those other projects as well. Be sure you have a strategy for which projects should share the permissions you're setting up, especially if your project contains data you don't wish for some users to be able to view.
Very likely, you'll want your private project to use a permission scheme that isn't shared.
(Optional) copy the permission scheme
This is only necessary if the project you created is already using a permission scheme shared with other projects. If it has its own scheme, skip this step.
You can determine which permission scheme each project is using across all of Jira by navigating to Settings (cog icon) > Issues > Permission schemes.
Edit the permissions on the scheme for your project
- プロジェクトへ移動する
- Click Project settings
- Click Permissions
- Click Actions
- Click on Edit permissions
- Click Update link for each permission
- Add the group or the project role you created during the Preparation section to all permissions
- Add the group or project role for any project administration to the Administer Projects permission
- Remove every other group, role, etc from all permissions
- Configure the project's remaining settings as needed for the project's intended work
- There is no one-size fits all approach to this step, so it won't be covered here
- Finally, remove yourself from the group/project role
You're all set! At this time, only the intended users and project administrator can access the project's issues and associated information, assuming they have been added to the project.
If it is ever necessary for you or another user to gain access to this project, adding said user to the group or project role will give them the ability to access the project. It's recommended to ensure there's always at least one active project administrator with access to the project to facilitate these changes.
重要な注意事項
- The project will be visible but not accessible to Jira global administrators
- The project will be listed under Projects, but even global admins cannot see issue data inside the project
- It will not be visible or accessible to any user who is not a global admin
- It will be visible, and accessible, to the users in the group or assigned the project role applied in the project's permission scheme
- This means that any site or organization admin can give themselves access to the Project by adding themselves to the group or project role
- It is not possible to prevent an Admin from doing this, but these actions will be recorded in the Audit Log if they are taken