Integration for Jira

Beezi uses Jira as a board integration provider to import tickets, synchronize task state, and run AI workflows directly against your engineering backlog. Once connected, Beezi can process Jira issues, generate implementation plans and code, and keep the ticket updated as work progresses.

Pricing & Availability

The Jira integration is a core feature included in both Free and Pro plans at no additional cost.

1. Installation & Configuration

Who Can Configure the Integration

Connecting Jira to Beezi requires administrative access in Beezi. This action can be performed by the following roles:

• Tenant Owner
• Tenant Admin

Once configured, the Jira connection is available within the relevant Beezi project workflow.

How to Connect

There are two ways to connect Jira to Beezi: during onboarding or later from the Projects panel.

Method A: During Onboarding

When creating or configuring your Beezi environment, you can connect Jira during the setup flow:

1. Select Jira as the board integration provider.
2. Click the Connect button.
3. You will be redirected to the Atlassian authentication page.
4. Sign in with your Atlassian account (Site Administrator/Project Administrator) and grant access to Beezi.
5. After authorization, select the Jira project you want Beezi to use.

Once completed, Beezi can begin importing and processing tickets from the selected Jira project.

Method B: Via the Projects Panel

If you skipped Jira during onboarding, you can connect it later from the Beezi platform:

1. Log in to Beezi and navigate to Projects.
2. Open the relevant project or create a new one.
3. Click Add Project Integration.
4. Select Jira.
5. Complete the same Atlassian authorization flow.
6. Choose the Jira project that should be linked to Beezi.

2. Authentication & User Matching

Authentication & Security

Beezi connects to Jira using Atlassian OAuth.

This means:

• Access is granted through the official Atlassian authorization flow.
• Beezi only accesses data that the authorized account can access.
• The connection can be revoked using your Atlassian account controls at any time.

User Matching

To associate Jira activity with the correct Beezi user, the system matches users by email address.

For this to work correctly, the email address in Jira must be visible.

Jira Email Visibility Requirement

Your Atlassian account email visibility must be set to Anyone.

Path:

1. Open Atlassian Account Settings
2. Go to Profile
3. Open Visibility
4. Set your email visibility to Anyone

IMPORTANT

If your Jira email visibility is restricted, Beezi may not be able to match users correctly. This can affect notifications, task ownership mapping, and automation behavior tied to the connected Jira project.

3. Repository Mapping

Beezi uses labels to map Jira work to the correct codebase.

How Repository Mapping Works

• Each connected repository in Beezi is associated with a label.
• That label is used to determine which codebase should be targeted for AI processing.
• When a Jira ticket includes the mapped label, Beezi routes the work to the corresponding repository.

This approach is especially useful when one Jira project supports multiple repositories or services.

NOTE

Repository access is limited to task execution only.

4. Features & Workflow

Ticket Import & AI Processing

After Jira is connected:

• Beezi can import Jira issues into the platform.
• Tickets can be queued for estimation, planning, and code generation.
• AI agents use the ticket description, metadata, and repository mapping to determine the implementation path.

Workflow Automation

Beezi automatically updates Jira ticket states as work progresses.

In Progress

Beezi moves the Jira ticket to In Progress when AI processing starts for the task.

IMPORTANT

The In Progress column or equivalent workflow state must exist in your Jira board configuration. If it does not exist, Beezi cannot move the ticket into that state automatically.

Completed

Beezi does NOT automatically move tickets to Completed/Done status.

Here's how the completion workflow works:

1. Beezi generates code and creates a Pull Request
2. Human review required: A developer must review the generated code
3. PR approval and merge: Developer approves and merges the PR through normal review process
4. Manual ticket closure: Developer manually moves the Jira ticket to Completed/Done status

This human-in-the-loop approach ensures:

• All AI-generated code is properly reviewed before being considered complete
• Team maintains full control over what gets merged
• Ticket status accurately reflects actual completion, not just code generation

Automated Comments

Beezi can add automated comments to the Jira issue to keep the task history visible in the board itself.

Typical examples include:

• Estimation completed - Task clarity score calculated
• Task processing started - AI workflow initiated
• Implementation plan attached - Detailed plan ready for review
• Pull request created - Code generation complete

These updates help keep Jira aligned with Beezi activity, even when implementation work is reviewed from Slack or Microsoft Teams.

5. Permissions & Security

Beezi requests the minimum scopes required to interact with your Jira workspace effectively.

Scope Name	Code	Description
View Jira issue data	read:jira-work	Read Jira project and issue data, search for issues, and objects associated with issues.
Create and manage issues	write:jira-work	Create and edit issues in Jira, post comments as the user, and create worklogs.
View user profiles	read:jira-user	View user information in Jira including usernames and email addresses.
Manage Jira webhooks	manage:jira-webhook	Fetch, register, refresh, and delete dynamically declared Jira webhooks.
View projects	read:project:jira	Permission to view projects within the Jira instance.
View boards and backlogs	read:board-scope:jira-software	View boards, issues on a board, backlogs, reports, and versions.
View board configuration	read:board-scope.admin:jira-software	View the configuration, project features, filters, and quick filters for a board.
Manage project settings	manage:jira-project	Create and edit project settings and create new project-level objects.
Manage global settings	manage:jira-configuration	Take Jira administration actions like creating projects and custom fields.
View priority schemes	read:priority-scheme:jira	View priority schemes used to configure default work item priorities.
Manage development info	manage:jira-data-provider	Manage development and release information for third parties in Jira.

Data Collection & Privacy

When you connect Jira to Beezi, we collect and process:

• Your Jira user ID and email address (for account matching).
• Access tokens (to read and update issues on your behalf).
• Ticket metadata, descriptions, and status information.
• Webhook delivery status and interaction metadata.

All data is stored securely using industry-standard encryption and is used solely to provide board integration services. We do not access Jira projects or issues that are not explicitly connected to your Beezi workspace.

6. Troubleshooting

Email Visibility Issues

Problem: Users not receiving notifications or tasks not properly assigned.

Solution:

1. Verify email visibility is set to "Anyone" in Atlassian account settings
2. Ensure the email in Jira matches the email in Beezi
3. Check that user has accepted Beezi workspace invitation

Ticket Status Not Updating

Problem: Beezi doesn't move ticket to "In Progress" when processing starts.

Solution:

1. Verify the "In Progress" status exists in your Jira workflow
2. Confirm OAuth connection hasn't expired - reconnect if needed
3. Check that the connected account has permission to edit issues

OAuth Token Expired

Problem: Integration suddenly stops working; error messages about authentication.

Solution:

1. Go to Beezi Projects → Select project → Integrations
2. Click "Reconnect" next to Jira integration
3. Complete OAuth flow again
4. Verify connection by importing a test ticket

Webhook Delivery Failures

Problem: Jira updates not triggering Beezi workflows in real-time.

Solution:

1. Verify firewall/network doesn't block Atlassian webhooks
2. Check webhook status in Beezi integration settings
3. Re-register webhooks:
   • Disconnect Jira integration
   • Wait 30 seconds
   • Reconnect Jira integration
4. Test with a manual ticket update

Cannot Find Specific Jira Project During Setup

Problem: Desired Jira project doesn't appear in selection list.

Solution:

1. Verify you have access to the project in Jira (must be project member)
2. Ensure project is a "Software" project type (not Service Desk or Work Management)
3. Check that OAuth account has permission to view the project
4. Try reconnecting with a Jira admin account if permissions are unclear

7. Important Information

AI-Generated Content Disclaimer

Beezi uses artificial intelligence (AI) and Large Language Models (LLMs) to assist with code generation and task implementation through our CODE_GEN feature.

IMPORTANT

While our AI strives for accuracy, it may occasionally generate incorrect, incomplete, or suboptimal responses. Please be aware that:

• Generated code should always be reviewed and tested before deployment.
• AI-generated implementations may not follow your specific coding standards or best practices.
• The AI may misunderstand task requirements or generate code with bugs or security vulnerabilities.
• Status updates reflect automation events and configured workflow mappings.
• Human approval is required at multiple stages: implementation plan review, code review, and final merge.

Best Practices

• Keep Jira ticket descriptions clear, technical, and complete with acceptance criteria and technical requirements.
• Use repository labels consistently so Beezi targets the correct codebase.
• Review implementation plans before approving code generation to verify the approach aligns with your architecture.
• Validate generated Pull Requests with your normal testing and review process before merging.
• Always run tests and validation checks on AI-generated code.
• Provide clear, detailed task descriptions for better results.

By using Beezi's AI features, you acknowledge that you understand the limitations of AI-generated content and will exercise appropriate oversight and validation.

8. Getting Help

If you encounter issues not covered in this troubleshooting guide:

• Support Email: hello@beezi.ai
• Check Beezi Status: Verify no ongoing service issues

When contacting support, include:

• Jira project name
• Beezi project/workspace ID
• Error messages or screenshots
• Steps to reproduce the issue