Connect Jira Data Center to Rovo

Centralize your team’s knowledge across Data Center and Cloud sites by integrating your Jira Data Center projects and issues into Rovo.

What is indexed?

The Jira DC connector indexes these objects:

• Projects (business, software, and service types)

• Issues

• Comments

For each relevant object, it indexes these attributes:

• Name

• Type

• Description

• Created date

• Last updated date

• Creator

• Last updated by

• Contributor

• Assignee

• Project

• Parent

• Labels

• Votes

• Watchers

• Reactions

• Status

• Subtype

• Priority

• Due date

• Resolution

• Environment

• Attachments

• Relationships

• Team

• URL

• Container key (for relationships, e.g., epic/project)

• Parent key (for subtask/parent relationships)

• Text/body (for comments)

Before you begin

• To connect Jira Data Center to Rovo, the minimum required version is Jira 11.0 and above, as well as in 10.3.10 LTS and later.

• You can connect up to three instances of Jira Data Center to your cloud site.

• Rovo will always respect permissions. Users will only ever see content that they already have access to. More on connectors and permissions

• Starting with Jira 11.3 in, we’re introducing a new way to link Data Center and cloud via cloud connectors. In this approach, application links remain the method of connection and are now enhanced with OAuth 2.0.

• If you’ve enabled rate limiting, you may need to adjust your request limits to ensure content is seamlessly indexed in Rovo.

Overview

If you’re ready to connect Jira Data Center to Rovo, follow these steps. The steps will differ based on the Jira Data Center version you’re using.

For Jira Data Center 11.3 or later, use Cloud connectors:

1. If your Data Center instance is hosted on private networks, create an application tunnel.

2. Connect Data Center to cloud with cloud connector.

3. Set up Rovo connector via cloud connector.

4. Choose which spaces to include.

For Jira Data Center 11.2 or earlier, use application links:

1. Create an application tunnel or configure an allowlist - This step only applies to Jira instances hosted on private networks. If your Jira instance is available over the public internet, skip this step.

2. Create an incoming application link.

3. Set up the connector in Atlassian Admin.

Connect to Rovo via cloud connector

These steps are applicable to Jira Data Center 11.3 and later. If you’re using earlier versions, check other connection options via application links.

Step 1: Set up an application tunnel

If your Jira Data Center instance is on a private network, you need to set up an application tunnel from your Cloud organization to your Jira Data Center instance. You can also use an existing tunnel by adjusting its configuration. More on tunnels

Create a new tunnel

1. Open Application tunnels in Atlassian Marketplace.

2. Install the Marketplace app in your Data Center instance.

3. Configure the required connections and upstream ports.

4. Go to Atlassian Administration. Select your organization if you have more than one.

5. Select Data management > Data sources > Application tunnels.

6. Select Create tunnel.

7. Go through the wizard to provide the details of your self-managed instance and generate the security key associated with your tunnel.

8. Add the key to your Jira Data Center instance.

   1. To be redirected to your instance, select Copy and process.

   2. To give the key to the admin of the instance, select Copy, then Close. The key can be added manually in Administration > Application tunnel, by selecting Add security key.

9. Paste your security key and follow the steps in the wizard.

Your tunnel is created. Wait until the status is Connected.

Use an existing tunnel

To use an existing tunnel, modify the HTTP connector:

1. In your installation directory, edit the conf/server.xml file.

2. Update the connector to include the attribute: secure="true".

More on required connections and upstream ports

Step 2: Set up сloud connector

In this step, you’ll create an organization-level сloud connector between your cloud organization and your Jira Data Center instance.

Follow the steps described in Configure cloud connectors, and then return to this page.

Step 3: Set up Rovo connector

In this step, you’ll need to switch between your cloud site and Data Center instance, so make sure to have them both open.

Create Rovo connector in cloud

1. Go to Connected sources page in your cloud Admin Hub. There’re two ways to open this page:

   1. On the Cloud connectors page in Data Center Jira administration, select Connect cloud apps. You’ll be redirected to the related page in cloud.
      
      

   2. In your cloud Admin Hub, go to Data Management, then Data sources, and then Connected sources.

2. Next to your organization connection, select Connect app.

3. On the Select an app to connect screen, select Atlassian Rovo.

4. On the Select site screen, select a cloud site that you’d like to connect Rovo to, and then select Next.

5. On the Check connection screen, we’ll run a check to reach your Data Center instance. If you have more than one application tunnel, select the needed one, and then select Next. If you don’t have an application tunnel, create one.

6. On the Send connection request screen, select Agree and continue.

7. Now that you’ve configured the connection on the cloud side, select Go to Data Center to finish the connection. If you don’t have the Data Center system admin permissions, ask the admin to continue the setup on the Data Center side.

Accept connection request in Data Center

1. On the Cloud connectors page in Jira admin screen, select Review request.

2. On the Review connection request screen, select Accept. Rovo is powered by Teamwork Graph, so it will appear with that name on the list.

Next steps

After you’ve finished connecting Jira Data Center, your team members will see Jira Data Center and Jira Service Management Data Center (if applicable) show up as a filters options in Search. They will be asked to connect before they can see results. This is required so Rovo can make sure your teammates only see results they have access to.

Connection statuses

There are different statuses on the Connected sources page that show how your Data Center instance is connected to Rovo. Here’s a brief overview of connection statuses as they appear in cloud and Data Center:

Revoke credentials

You can revoke credentials and disable the connector if there’s a chance that the credentials were exposed and are no longer safe.

To revoke Rovo credentials:

1. Go to your Data Center instance, go to Administration, find Application links, and then go to Cloud connectors.

2. Select More actions (), and then Revoke credentials.

3. Confirm your action by selecting Revoke credentials. The connector status will change to Disabled.

Rotate credentials

You can rotate Rovo credentials when they expire or after they’ve been revoked.

To rotate Rovo credentials:

1. In your cloud Admin Hub, go to Data Management, then Data sources, and then Connected sources.

2. Find your organization connector and expand it.

3. Next to Rovo connection, select More actions (), and then Rotate credentials.

4. Confirm your action by selecting Rotate credentials. Wait up to 30 minutes while the credential rotation takes place. The connector will change status to Connected.

Delete connector

You can delete and re-establish Rovo connector as many times as you need. The connector should be in Connected status to be deleted.

To delete Rovo connector from Data Center:

1. Go to your Data Center instance, go to Administration, find Application links, and then go to Cloud connectors.

2. Select More actions (), and then Delete connector.

3. Confirm your action by selecting Delete.

To delete Rovo connector from cloud:

1. In your cloud Admin Hub, go to Data Management, then Data sources, and then Connected sources.

2. Find your organization connector and expand in.

3. Next to Rovo connector, select More actions (), and then Delete connector.

4. Confirm your action by selecting Delete.

The connector will disappear from both cloud and Data Center admin panels.

Connect to Rovo via application links

These steps are applicable to Jira Data Center 11.2 and earlier. If you’re using newer versions, consider using the connection option via Cloud connectors.

Step 1: Set up an application tunnel

If your Jira Data Center instance is on a private network, you need to set up an application tunnel from your Cloud organization to your Jira Data Center instance. You can also use an existing tunnel by adjusting its configuration. More on tunnels

Alternatively, if you prefer not to use tunnels, you can allowlist incoming connections or IPs for Atlassian Cloud products and sites in your Data Center instance. More on IP addresses and domains for Atlassian Cloud products

Create a new tunnel

1. Open Application tunnels in Atlassian Marketplace.

2. Install the Marketplace app in your Data Center instance.

3. Configure the required connections and upstream ports.

4. Go to Atlassian Administration. Select your organization if you have more than one.

5. Select Data management > Data sources > Application tunnels.

6. Select Create tunnel.

7. Go through the wizard to provide the details of your self-managed instance and generate the security key associated with your tunnel.

8. Add the key to your Jira Data Center instance.

   1. To be redirected to your instance, select Copy and process.

   2. To give the key to the admin of the instance, select Copy, then Close. The key can be added manually in Administration > Application tunnel, by selecting Add security key.

9. Paste your security key and follow the steps in the wizard.

Your tunnel is created. Wait until the status is Connected.

Use an existing tunnel

To use an existing tunnel, modify the HTTP connector:

1. In your installation directory, edit the conf/server.xml file.

2. Update the connector to include the attribute: secure="true".

More on required connections and upstream ports

Step 2: Create an incoming application link

Create an application link in the administration of your Jira Data Center instance to use in the connection process. About creating application links

1. In Jira Data Center, go to Administration > Application Links.

2. Select Create link.

3. Choose External application > Incoming.

4. Select Continue.

5. Enter a name for your application link

6. Insert https://id.atlassian.com/outboundAuth/finish as the redirect URL.

7. For application permissions, select Manage Subscriptions.

8. Select Save.

9. In the application links table, under Actions, select More actions (•••) > View credentials.

10. Make note of the Client ID and Client secret - you’ll need them when setting up the connector in Atlassian Admin.

Step 3: Set up the connector in Atlassian Admin

Access the setup screen for the Jira Data Center connector in Atlassian Admin:

1. Go to Atlassian Administration. Select your organization if you have more than one.

2. Select Apps > AI settings > Rovo.

3. Under Sites, next to the site you want to connect, select Add connector.

4. Select Jira Data Center and press Next.

Configure Jira Data Center:

1. Enter a name for your Jira Data Center connection.

2. Select your Data Center network type:

   1. Private network if your network is behind a firewall and can’t be accessed over the public internet. Select the application tunnel you previously set up.

   2. Public network if your Jira Data Center instance can be accessed over the public internet or you’ve allowlisted incoming connections or IPs instead of using tunnels. Insert the server base URL (including context path if applicable) of your Jira Data Center instance.

3. Enter the OAuth Client ID and Client secret.

4. Review the disclaimer.

5. Select Authorize Jira Data Center.

Next steps

After you’ve finished connecting Jira Data Center, your team members will see Jira Data Center and Jira Service Management Data Center (if applicable) show up as a filters options in Search. They will be asked to connect before they can see results. This is required so Rovo can make sure your teammates only see results they have access to.