Adding Jira organization to GitProtect

This article describes the process of adding a Jira organization to GitProtect.

Adding Jira organization to GitProtect connects your environment to the platform so you can start protecting its data.

Using an API token

For Jira, use the classic token — GitProtect does not support scoped tokens.

Before adding your Jira organization to GitProtect, check if your account has all the required permissions for projects and spaces you want to secure.

Log in to GitProtect Management Service, open the DevOps tab on the left side of the window, and select Jira from the list.

Click the Connect button under Jira Software or Jira Service Management (depending on your needs).

Enter your instance URL (i.e., https://instancename.atlassian.net) and your Jira login, then add or select an API token from the Password Manager.

GitProtect can secure organizations that have a custom domain added, but you must add the instance using its original URL, which you can find in in https://admin.atlassian.com > App URLs > Custom domains > Actions > Show details. Learn more about custom domains in this article.

Configure your spaces sync and default worker — specify hours for synchronization, or set a time interval for automatic updates. Once done, click Proceed.

The account used for the authorization process must have at least site admin permissions.

Your Jira organization has now been successfully added to GitProtect. Granular backup is the default policy configuration applied to any new Jira organization you add to GitProtect — click Customize policy to adjust your backup policy settings, or click Run now to execute the backup immediately using the current policy configuration.