Atlassian Agent

This page provides detailed configuration instructions for the Atlassian Agent, which enables integration with Jira and Confluence for automated issue management, content extraction, advanced search

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:

Permission	Type	Description
offline_access	Delegated	Maintain access to data you have given it access to
read:confluence-space.summary	Delegated	View summary information about Confluence spaces
read:confluence-props	Delegated	View Confluence content properties
read:confluence-content.all	Delegated	View all Confluence content (pages, blogs, etc.)
read:confluence-content.summary	Delegated	View summary information about Confluence content
read:confluence-content.permission	Delegated	View permissions for Confluence content
read:confluence-user	Delegated	View Confluence users
read:confluence-groups	Delegated	View Confluence groups
readonly:content.attachment:confluence	Delegated	View attachments in Confluence content
search:confluence	Delegated	Search Confluence content
read:jira-work	Delegated	Read access to Jira issues, projects, workflows, and work items
read:jira-user	Delegated	View Jira users and their profiles for assignment operations
read:project:jira	Delegated	Read access to Jira project details, configurations, and metadata
read:board-scope:jira-software	Delegated	View Jira Software boards, sprints, and agile project data
write:jira-work	Delegated	Create, edit, update, and manage Jira issues and work items

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

Scope clarification: The Atlassian Agent connects to two products with distinct permission requirements:

• Jira: Requires specific Read & Write scopes to enable comprehensive issue operations (create, edit, assign, transition, search). Configure the granular Jira scopes listed in the permissions table above for optimal functionality.

• Confluence: Uses read-only access for search and content retrieval. Configure only the Confluence read scopes listed above (no write scopes needed).

Recommendation: Configure both Jira and Confluence scopes as listed in the permissions table, or use the .default scope for comprehensive access to both products.

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 Atlassian OAuth Credentials:

   • Client ID: Enter the Client ID from your Atlassian OAuth app

   • Client Secret: Paste the client secret you generated

   • Redirect URL: Verify https://nango.theblockbrain.ai/oauth/callback is configured

3. Configure Dual Integration Connectors:

   • The Atlassian Agent includes two separate connectors:

     • Jira Connector: For issue management and project operations

     • Confluence Connector: For documentation search and content retrieval

   • Configure each connector individually in the admin interface

   • Important: Both connectors must be visible and configured for full functionality

4. Configure OAuth Scopes:

   • Add required scopes for both Jira and Confluence using the "Add" button as mentioned here

   • Each scope will appear as a removable tag

   • Use the "X" button to remove incorrect scopes

5. Additional Configuration (Optional):

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

   • Configure any organization-specific settings

6. Save Configuration:

   • Click "Save" to apply the settings

   • Wait for the confirmation message

   • Verify both Jira and Confluence connections are active

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:

• User Training: Train users on both Jira and Confluence integration features

• Permission Review: Regularly audit user access to ensure appropriate Atlassian permissions

• Integration Monitoring: Monitor both connectors for ongoing functionality

• Feature Adoption: Encourage teams to leverage cross-platform capabilities (Jira-Confluence linking)

• Support Documentation: Share common use cases and troubleshooting guides with end users