Connect Jira Cloud

This page describes how to connect Jira Cloud to Agentspace.

After you set up your data source and import data the first time, the data store syncs data from that source at a frequency that you select during setup.

Supported versions

The Jira Cloud connector supports version 2 of the JIRA Cloud REST API.

Before you begin

Before you set up your connection, do the following:

• Verify that you have Jira organization administrator access to the Jira instance and project. With the organization administrator access, you can set up minimum permissions and provide access privileges to user groups. For information about how to verify Jira organization administrator access, see Verify Jira organization administrator access .

• (Optional) To retrieve user email addresses from Jira Cloud, even when settings restrict email visibility, install the User Identity Accessor for Jira Cloud app. You must be a Jira Site administrator to install and configure this app. After you install the app, configure it to securely retrieve user email addresses. You might not need to install this app if email addresses are already publicly accessible.

• To enforce data source access control and secure data in Agentspace, ensure that you have configured your identity provider .

• To enable OAuth 2.0 and obtain the client ID and secret, see OAuth 2.0 (3LO) apps in the Atlassian developer documentation.

Verify Jira organization administrator access

1. Login to Atlassian with your user credentials.

2. Select the Jiraapp.

   

3. Click Settings.

   If you see the Systemoption under Jira settings, you have Jira organization administrator access. Otherwise, request your Jira organization administrator to provide access.

   

Create an OAuth 2.0 integration

1. Sign in to the Atlassian Developer Console .

2. Click the profile icon and select Developer console.

   

3. Click Createand select OAuth 2.0 Integration.

   

4. Enter a name for the app.

5. Select the checkbox to agree to Atlassian's developer terms.

6. Click Create.

   

7. Click Authorization.

8. In the Authorization typetable, select Addfor OAuth 2.0 (3LO).

   

9. In the Callback URLfield, enter https://vertexaisearch.cloud.google.com/console/oauth/jira_oauth.html .

10. Click Save changes.

    

Configure the minimum permissions required for the application

1. On the application page, click Permissions.

   

2. Go to Jira APIand click Add.

3. Click Configure.

4. Go to the Classic scopestab.

5. Click Edit scopesand select the following permissions:

   • read:jira-user
   • read:jira-work

   

6. Confirm that the two scopes are selected, and then save your changes.

7. Go to the Granular scopestab.

8. Click Edit scopesand select the following permissions:

   • read:issue-security-level:jira
   • read:issue-security-scheme:jira
   • read:group:jira
   • read:user:jira
   • read:avatar:jira
   • read:audit-log:jira

   

Minimum permissions

The following tables list the minimum permissions required to create a Jira Cloud connector.

Classic scopes

Granular scopes

Obtain a client ID and client secret

1. Click Distributionand select Edit.
2. Select Sharingto enable editing other fields.
3. Fill out the remaining fields:
   1. For Vendor, enter Google .
   2. For Privacy policy, enter https://policies.google.com .
   3. For Does your app store personal data?, select Yes.
   4. Select I confirm that I've implemented the personal data reporting APIcheckbox. For more information, see Personal data reporting API .

      

4. Click Save changes.

5. Click Settingsto copy your Client IDand Client secret.

   

Obtain an instance ID and instance URL

1. Obtain the instance ID:

   1. Open a new tab, copy the instance URL, and append /_edge/tenant_info to the instance URL. For example, https:// YOUR_INSTANCE .atlassian.net/_edge/tenant_info .

   2. Navigate to the link to find the cloudId value. The cloudId is your instance ID.

      

2. Obtain the instance URL:

   1. Go to atlassian.net and sign in with your administrator account.
   2. Select the app you want to sync. For example, sync the first app.
   3. Find the instance URL (the subdomain in the address bar).

Grant administrator roles

To grant the Jira administrator the Discovery Engine Editor role in the Google Cloud console, do the following:

1. In the Google Cloud console, go to the Agentspacepage.

2. Navigate to IAM.

   Go to IAM

3. Locate the user account which has administrator access in Jira and click the Editicon edit .

4. Grant the Discovery Engine Editor role to the administrator .

To grant a user an administrator role in Atlassian, do the following:

1. Sign in to Atlassian using an organization administrator account.

2. Click the menu icon and select your organization. Alternatively, you can go to admin.atlassian.com .

3. On the Adminpage, click the product and select the Manage usersbutton.

   

4. Click Groupsunder User management.

5. On the Groupspage:

   1. Click Create group.
   2. Enter a name for the group.

   

This group receives permissions required by the connector. Users added to this group inherit these permissions.The connector uses this group to authenticate and fetch documents.

1. On the group page, click Add product.

2. Select User access adminas the role for Jira.

3. Select Product adminas the role for Jira administration.

   

4. Click Grant Access.

5. Click Add group membersto add a user account or group members that the connector uses to authenticate and access the required resources.

   

Manage user visibility

To make the user's email visible to anyone in the Atlassian account, follow these steps:

1. Sign in to the Atlassian Developer Console .

2. Click the profile icon and select Developer console.

3. Click the user profile icon and select Manage account.

   

4. Navigate to the Profile and visibility.

   

5. Go to Contactand set the Who can see thisas Anyone.

   

To make the user's email visible to anyone in the Jira, follow these steps:

1. Sign in to Atlassian with your user credentials.

2. Select a Jira app.

3. Click Settings> System.

4. Select General Configurationin the left pane.

5. Click Edit Settings.

6. For User email visibility, select Public.

   

7. Click Update.

Install and configure User Identity Accessor for Jira Cloud

If user email addresses aren't publicly accessible by default due to privacy settings in Jira Cloud, you must install the User Identity Accessor for Jira Cloudapp to securely retrieve user email addresses. If user email addresses are already publicly visible, you might not need to install the app. For more information about restricted email visibility, see Manage user visibility .

Roles and permissions

To install and configure the User Identity Accessor for Jira Cloudapp, you must have the appropriate administrative role and grant the required app-level permissions.

• Required role: You must be a Jira Site administrator to install and configure the app.
• App-level permissions: You must grant the following permissions during the app installation:
  • Read Email Address : Allows the app to securely retrieve user email addresses, even when profile visibility is restricted.
  • App Storage scope : Enables the app to read and write to its storage device.

Install User Identity Accessor for Jira Cloud

To install the User Identity Accessor for Jira Cloudapp on your Jira Cloud site, follow these steps:

1. Navigate to Atlassian Developer Console .

2. Review the Read Email Addressand App Storage scopepermissions and click Get app.

   

3. From the Select a site to install this app onlist, select the Jira site where you want to install the app. This list displays only the sites for which you have administrator access.

   Note:You must be an administrator of at least one Jira site to install the app.

4. Click Installto complete the app installation.

Configure User Identity Accessor for Jira Cloud

After you've installed the User Identity Accessor for Jira Cloudapp, configure an API key that your external system (for example, your Jira Cloud Connector) uses to securely call the app's web trigger to fetch emails.

Access the configuration page

To access the User Identity Accessor for Jira Cloudapp's configuration page, follow these steps:

1. In your Jira Cloud instance, click the Settings⚙️ icon in the navigation menu.
2. Select Appsfrom the menu.
3. On the Apps administrationpage, locate your app, User Identity Accessor for Jira Cloud, in the Manage appslist.

4. Click Configureor the link associated with your app. The app's dedicated configuration page opens within Jira Cloud.

   

Set up the API key

To set up the API key on the configuration page, follow these steps:

1. In the API Key Configurationsection, specify the secret key for authenticating requests to the app's webtrigger. You can authenticate requests using either of the following methods:

   • Enter your own key: Type or paste your own strong, unique API key into the API Key field. Use a key of at least 20–30 characters with a mix of uppercase letters, lowercase letters, numbers, and symbols.

     

   • Generate a key: Click the Generate New Keybutton. The system generates and displays a strong, random key in the field.

     

     Important: Immediately copy the API key displayed in the field. For security reasons, you might be unable to view the full key again after saving or navigating away. If lost, you need to set or generate a new one.

2. Click Save API Key. A success message confirms that the key is securely saved.

Test the app configuration

Verify if the User Identity Accessor for Jira Cloudapp is configured correctly by sending a request from your external system and confirming that user email addresses are returned successfully.

Get the webtrigger URL

1. On the Apps administrationpage, locate the Webtrigger URLsection, which displays the unique URL specific to your Jira site and this app installation:
   • Your external system must call this URL to request user emails.
   • The URL typically looks like: http://uuid/domain.net/x1/randomId . For example, https:// YOUR_INSTANCE_ID .hello.atlassian-dev.net/x1/ WEBTRIGGER_ID , where YOUR_INSTANCE_ID is your Jira Cloud instance identifier and WEBTRIGGER_ID is the unique identifier for the webtrigger endpoint generated for your app.
2. Click the Copy URLbutton or copy the entire URL.

Configure your external system

• Configure your external system that needs to fetch Jira user emails with the API key and webtrigger URL obtained in the previous steps.

• Endpoint URL: The webtrigger URL you copied.

• HTTP Method: POST

• Required Headers:

  • Content-Type: application/json

  • X-Api-Key: YOUR_API_KEY

    Replace YOUR_API_KEY with the API key you set or generated in the Set up the API key section.

Example curl command

This example demonstrates calling the User Identity Accessor for Jira Cloudwebtrigger, which accepts an array of account IDs and returns the email addresses.

 curl  
--location  
--request  
POST  
 'https:// YOUR_INSTANCE_ID 
.hello.atlassian-dev.net/x1/ ENDPOINT_PATH 
' 
  
 \ 
--header  
 'X-Api-Key: YOUR-API-KEY 
' 
  
 \ 
--header  
 'Content-Type: application/json' 
  
 \ 
--data-raw  
 '{ 
 "accountIds": [ 
 " ACCOUNT_ID_1 
", 
 " ACCOUNT_ID_2 
" 
 ] 
 }' 
 

Replace:

• YOUR_INSTANCE_ID with your Jira Cloud instance ID
• ENDPOINT_PATH with the API endpoint path
• YOUR_API_KEY with the API key you set or generated in the Set up the API key section
• ACCOUNT_ID with Atlassian account IDs you want to target

Expected response

  [{ 
 "accountId" 
 : 
 " ACCOUNT_ID_1 
" 
 , 
 "emailAddress" 
 : 
 " EMAIL_ADDRESS_1 
" 
 }, 
  
 { 
 "accountId" 
 : 
 " ACCOUNT_ID_2 
" 
 , 
 "emailAddress" 
 : 
 " EMAIL_ADDRESS_2 
" 
 }] 
 

Replace:

• ACCOUNT_ID_X with actual Atlassian account IDs
• USER_EMAIL_X with user email addresses returned from your API call

Implement security best practices

To confirm the security of your API key, follow these recommendations:

• Store the API key securely within your Jira Cloud Connector's configuration.
• Verify that all communication with the webhook URL occurs over HTTPS. This is the default for User Identity Accessor for Jira Cloudwebtriggers.

Support for User Identity Accessor for Jira Cloud

Support offerings are available from Google for the User Identity Accessor for Jira Cloudapp that can include maintenance and regular updates to keep the app up-to-date. If you encounter any issues or have questions specific to the app functionality, contact Google Cloud Support . For more information, see Getting Cloud Customer Care .

Create a Jira Cloud data store

Error messages

The following table describes the common error messages, their descriptions, and possible solutions when connecting Jira Cloud with Agentspace.

Known limitations

• For unstructured data, each media type has different restrictions. For more information, see Prepare data for custom data sources .

• For structured data, each document must not exceed 500 KB in size.

• Application roles with specific, non-empty roles cannot be granted Browse project or security level permissions.

• Document permissions determined by user custom fields or group custom fields are not supported.

• Jira Cloud does not allow any restrictions on worklog levels.

• Attachments added to private comments don't inherit the access restrictions (ACLs) on the comments.

• Only the previous 20 comments for an issue in Jira Cloud are fetched.

• Sprint tables can't be ingested.

• The legacy user management model is not supported for integration with Jira Cloud. Only the centralized user management model is supported. For more information, see Atlassian Organization consolidation guide .

Next steps

• To attach your data store to an app, create an app and select your data store following the steps in Create an app .

• To preview how your search results appear after your app and data store are set up, see Preview search results .

• To enable alerts for the data store, see Configure alerts for third-party data stores .