Atlassian Agent

Overview

• Search and retrieve Jira issues and Confluence pages through Blockbrain

• Create, update, and manage Jira tasks, issues, and projects

• Extract and summarize content from Confluence spaces and pages for reporting or AI analysis

• Access project, issue, and page metadata for enhanced workflow automation

• Automate processes and reporting across Jira and Confluence using Atlassian data

Prerequisites

• Complete the general setup steps from the main AI Agents page

• Ensure users have active Atlassian Cloud accounts with access to Jira and/or Confluence

• Verify appropriate Atlassian product licensing for Jira and Confluence

Atlassian App Registration Configuration

Required API Permissions

Add the following Atlassian API permissions (OAuth 2.0 scopes) to your app registration:

As alternative, you can use the .default scope (uses all scopes set in the app)

Redirect URL

• Add https://nango.theblockbrain.ai/oauth/callback as allowed redirect URL to your app registration

Permission Configuration Steps

1. In your Atlassian developer console, go to your app’s OAuth 2.0 (3LO) configuration

2. Click "Add scopes"

3. Search for and select each required permission scope (see table above)

4. Click "Add" to include the selected scopes in your app

5. Save your changes

6. (Recommended) Have an Atlassian admin grant consent for all required scopes for organization-wide deployment

Agent Configuration in Blockbrain

1. Access Agent Settings:

   • Navigate to your Blockbrain admin panel

   • Go to Agents > Atlassian Agent

   • Click "Configure"

2. Enter Azure Credentials:

   • Client ID: Enter the Application ID from your Azure app registration

   • Client Secret: Paste the client secret you generated

   • Tenant: Enter your Azure tenant ID

3. Configure OAuth Scopes:

   • Add each required scope individually using the "Add" button as mentioned here

   • Each scope will appear as a removable tag

   • Use the "X" button to remove incorrect scopes

4. Additional Configuration (Optional):

   • Add custom key-value pairs if needed for specific requirements

   • Configure any organization-specific settings

5. Save Configuration:

   • Click "Save" to apply the settings

   • Wait for the confirmation message

Alternative: Admin Consent Configuration

For simplified scope management with admin pre-approval:

1. In the Atlassian Developer Console, have an admin grant consent for all required permission scopes.

2. In Blockbrain configuration, use the .default scope instead of individual scopes.

3. This eliminates the need for users to consent to individual permissions.

Testing the Atlassian Agent

Verification Steps

1. Connection Test:

   • Use the built-in connection test in Blockbrain.

   • Verify successful authentication with the Atlassian API.

2. User Testing:

   • Have a test user connect their Atlassian account.

   • Attempt to access a known Jira issue or Confluence page.

   • Verify issue/page retrieval and search functionality.

3. Permission Validation:

   • Check that the agent can access the appropriate Jira projects and Confluence spaces.

   • Confirm read/write permissions are working correctly.

Common Atlassian Integration Use Cases

• Issue Search: Find Jira issues across multiple projects.

• Content Extraction: Access and summarize Confluence pages for AI analysis.

• Project Navigation: Browse Jira project structures and Confluence spaces.

• Metadata Retrieval: Retrieve issue properties, page metadata, and comments.

Troubleshooting

Authentication Issues

Problem: "Access denied" or authentication failures

• Solution: Verify admin consent is granted for all required Atlassian API permissions scopes

• Check: Ensure the redirect URL is exactly https://nango.theblockbrain.ai/oauth/callback

Permission Errors

Problem: "Insufficient privileges" when accessing Jira or Confluence

• Solution: Confirm the app registration has all necessary Jira and Confluence API scopes.

• Check: Verify the user has access to the relevant projects and spaces in your Atlassian organization.

Scope Configuration Issues

Problem: Scopes not saving correctly

• Solution: Add each scope individually using the "Add" button

• Check: Remove any duplicate or incorrect scopes using the "X" button

Security Considerations

• Data Access: The agent inherits the user's Atlassian permissions.

• Project/Space Scope: Access is limited to projects and spaces the authenticated user can access.

• Data Privacy: Data is processed according to Blockbrain's data handling policies.

• Audit Trail: Atlassian access is logged in both Atlassian Cloud and Blockbrain audit logs.

Next Steps

After successful Atlassian Agent configuration:

• Train users on Atlassian integration features