Leverage Atlassian Integration with Hatz AI: Features and Tools Guide
Connect your Atlassian account to Hatz AI and work with Jira, Confluence, Compass, and Jira Service Management (JSM) directly from your conversations and workflows - no tab-switching required.
The integration of Atlassian and Hatz AI unlocks powerful opportunities for users looking to streamline project management, documentation, and service management workflows. Whether you're triaging issues, searching knowledge bases, or building automated pipelines, this fusion brings exceptional capabilities to your fingertips.
This guide will walk you through the features and tools provided by the Atlassian integration with Hatz AI's capabilities.
What is the Atlassian Tool?
The Atlassian tool is a comprehensive integration that allows users to connect and interact directly with multiple Atlassian products through a single connection. It supports four core Atlassian products: Jira (project management), Confluence (documentation and knowledge management), Compass (component tracking), and Jira Service Management (service desk operations).
With Hatz AI now connected to this tool, you can search, read, create, and update content across all four platforms without leaving your chat interface or workflow.
How and What Can a User Access?
Each user on the Hatz platform is required to connect their individual Atlassian account through a secure OAuth flow. This process involves authenticating with your Atlassian credentials and authorizing Hatz AI to access your workspace.
The connection uses Atlassian's official OAuth flow, ensuring that your credentials are never stored by Hatz AI. The integration strictly complies with Atlassian's security protocols while respecting the access permissions and rules assigned to each user's account.
It is important to note that the Hatz Atlassian integration will never exceed the access levels granted to the user within Atlassian, guaranteeing alignment with the platform's governance policies. As a result, outcomes and available features may vary depending on each user's specific permissions and authenticated access.
How to Connect:
Open the Connections page from your settings or Workshop.
Find Atlassian in the integration list and click Connect.
You'll be redirected to Atlassian to sign in and authorize access.
Once you approve, you're taken back to Hatz AI - the integration is ready to use.
You can revoke access at any time from your Atlassian account settings.
Features of the Atlassian Integration Tool
1. Jira - Issue and Project Management
Search and Retrieve Issues: Find Jira issues using filters, keywords, project keys, and assignees.
Create and Update Issues: Add new issues or modify existing ones with details like summary, description, priority, and labels.
Transition Issues: Move issues through your workflow stages (e.g., from "In Progress" to "Done").
Browse Projects and Components: Access project structures, component lists, and organizational hierarchies.
View Details: Look up issue details including comments, statuses, attachments, and history.
2. Confluence - Documentation and Knowledge Base
Search Across Spaces and Pages: Find content using keywords, space names, or page titles.
Read Page Content: Retrieve full page content and blog posts in readable format.
Create and Update Pages: Draft new Confluence pages or modify existing documentation.
Browse Space Structure: Navigate through spaces and their organizational hierarchy.
3. Compass - Component Management
View and Manage Components: Access component information and metadata.
Check Alerts and Health: Monitor component health status and active alerts.
4. Jira Service Management (JSM)
Service Request Management: Work with service desk tickets, queues, and customer requests.
Why Use the Atlassian Integration with Hatz AI?
Connecting your Atlassian workspace to Hatz AI allows you to:
Eliminate Context Switching: Access and update Jira issues, Confluence pages, and service requests without leaving your AI conversation or workflow.
Automate Routine Tasks: Build workflows that automatically create tickets, update documentation, or triage service requests based on triggers.
Accelerate Information Retrieval: Ask natural language questions to quickly find relevant issues, documentation, or component data.
Streamline Collaboration: Pull information from multiple Atlassian products in a single query to get a complete picture.
Boost Productivity: Let Hatz AI handle repetitive Atlassian tasks so your team can focus on high-value work.
Real-Life Use Cases
Scenario 1: Automated Bug Triage and Ticket Creation
A user discusses a bug in chat with Hatz AI. The AI analyzes the conversation, searches existing Jira issues to check for duplicates, and then creates a new Jira ticket with the appropriate project, priority, and labels - all without the user opening Jira.
Scenario 2: Knowledge Base Search and Summary
A new team member asks Hatz AI, "What's our deployment process?" The AI searches Confluence for deployment-related pages, retrieves the most relevant documentation, and provides a concise summary with links to the full pages.
Scenario 3: Weekly Project Status Report
A project manager builds a workflow that runs every Monday morning. It searches Jira for all issues updated in the past week within specific projects, summarizes the activity, and posts a formatted status report to the team's collaboration channel.
Atlassian & Hatz AI: Use Case List
This list outlines practical applications of the Hatz AI and Atlassian integration. It is categorized by the core features available through the tool, providing examples of direct Chat Prompts for quick, ad-hoc tasks and Workflows that can be built for more structured, repeatable automation.
1. Jira Issue Management
Use Case | Description | Chat Prompt Example | Workflow for Automation |
Quick Issue Search | Find issues assigned to you or matching specific criteria without opening Jira. |
| Daily Standup Prep Workflow: |
Create Issues from Conversations | Turn discussions or discovered bugs into properly formatted Jira tickets instantly. |
| Bug Intake Workflow: |
Issue Status Updates | Transition issues through your workflow or update fields without navigating the Jira UI. |
| Sprint Close-Out Workflow: |
2. Confluence Documentation
Use Case | Description | Chat Prompt Example | Workflow for Automation |
Search Documentation | Quickly find relevant documentation or policies across your Confluence spaces. |
| Onboarding Knowledge Retrieval Workflow: |
Summarize Pages | Get AI-powered summaries of long Confluence pages to quickly extract key information. |
| Weekly Documentation Digest Workflow: |
Create or Update Pages | Draft new documentation or update existing pages directly from your chat or workflow. |
| Meeting Notes to Confluence Workflow: |
3. Cross-Product Workflows
Use Case | Description | Chat Prompt Example | Workflow for Automation |
Issue Research | Combine Jira issue details with related Confluence documentation for complete context. |
| Epic Context Builder Workflow: |
Service Desk Automation | Automatically create Jira Service Management tickets from customer inquiries or detected issues. |
| Support Ticket Triage Workflow: |
Authentication and Access
Individual Connection Required: Each user must connect their own Atlassian account. There is no shared team connection.
Permission Boundaries: The integration can only access resources that the authenticated user has permission to view or modify in Atlassian. If a user cannot view a Jira project or Confluence space in Atlassian, they cannot access it through Hatz AI.
OAuth Only: The connection uses Atlassian's OAuth flow. API keys or password authentication are not supported.
Product-Specific Constraints
Compass Access: Compass functionality requires that Compass is enabled in your Atlassian workspace. Not all Atlassian plans include Compass.
JSM Access: Jira Service Management features are only available if JSM is enabled in your Atlassian instance and the user has appropriate service desk permissions.
Confluence Restrictions: Creating or updating Confluence pages requires write permissions in the target space. Users with read-only access can search and retrieve pages but cannot modify them.
Jira Workflow Rules: Issue transitions must comply with your Jira workflow configuration. The integration cannot bypass workflow rules or required fields.
Known Constraints
Single Atlassian Instance: The integration connects to one Atlassian workspace per user. If you have multiple Atlassian instances, you must choose which one to connect.
No Attachment Uploads: The current integration cannot upload file attachments to Jira issues or Confluence pages.
Search Scope: Search results may be limited by Atlassian's API rate limits or pagination constraints for very large result sets.
