Connect Jira to B6AI

Overview

The Jira integration lets bots and agents turn conversations into tracked work. When a customer reports a bug or requests a feature, B6AI can create a Jira issue in the right project, with the conversation attached.

Nothing gets lost between support and engineering, every request lands in your backlog.

What you can do with Jira

Once connected, your bots and agents can use Jira inside conversations and automations. Typical uses include:

1. Create an issue (bug, task or story) from a conversation.
2. Add comments and attach the transcript to an existing issue.
3. Update an issue’s status or assignee.
4. Look up an issue’s status by key and report it back in chat.
5. Link the issue back to the originating conversation for traceability.

How the integration works

B6AI calls the Jira Cloud REST API against your site (yourco.atlassian.net). You can use a Basic-auth API token (an account email plus the token) for a single site, or OAuth 2.0 (3LO) for consented, revocable access.

Calls act with the permissions of the account the credentials belong to, so ensure it can create issues in the target project.

Prerequisites

Make sure all of the following are in place before you start. Each one is required, skipping any will cause the connection to fail later.

1. A Jira Cloud site and an account that can create issues in the target project.
2. Your Jira site URL and the target project key.
3. The Enterprise Admin role in B6AI.

Choose a connection method

B6AI supports more than one way to connect Jira. Pick the one that fits your organization’s policies, the rest of this guide works for either.

Generate your Jira API token (or OAuth 2.0 credentials)

B6AI authenticates with Jira using your Jira API token (or OAuth 2.0 credentials). Follow these steps exactly, each field you copy here is entered into B6AI later.

1. Go to id.atlassian.com/manage-profile/security/api-tokens.
2. Click Create API token, label it “B6AI”, and Copy the token.
3. Note the email address of that Atlassian account.
4. Note your Jira site URL (https://yourco.atlassian.net) and the target Project key (for example SUP).

Required permissions & scopes

Grant only the scopes below. Each one maps to a specific B6AI capability; requesting fewer reduces risk and speeds up any review your Jira administrator performs. The table explains exactly what each scope allows and why it is needed.

Finish configuration inside Jira

Complete these steps in the Jira console before connecting B6AI, so the credentials are fully active.

1. For the API-token method, make sure the account has the Create Issues permission in the target project.
2. For OAuth, add the scopes above, register the B6AI redirect URL, and distribute the app to your site.

Connect Jira in B6AI

Now enter your credentials in B6AI. Signed in as an Enterprise Admin, open Settings → Integrations, find the Jira card and click Connect, then complete the form. Every field is explained below.

1. In B6AI, open Settings → Integrations → Jira.
2. Choose API token or OAuth.
3. Enter your site URL, account email and API token (or complete OAuth).
4. Select a default project key and issue type.
5. Click Save: B6AI reads the project to confirm access.

{
  "provider": "jira",
  "site_url": "https://yourco.atlassian.net",
  "email": "jira-bot@yourco.com",
  "api_token": "ATATT…",
  "project_key": "SUP",
  "issue_type": "Task"
}

Verify the connection

Confirm the integration is live before you rely on it in a bot.

1. Confirm the Jira card shows “Connected”.
2. Run the test: it creates a test issue in your default project.
3. Open Jira and confirm the issue exists, then transition or delete it.

Troubleshooting

If the connection fails or an action does not work, match the symptom below to its cause and fix.

Limitations & rate limits

Keep these constraints in mind so your bots behave predictably at scale.

1. Jira Cloud applies per-site REST rate limits and may return 429.
2. Available fields depend on your project’s screens and schemes.
3. API-token calls act as a single user.

Security best practices

1. Grant only the scopes and permissions listed above, never request more “just in case”.
2. Rotate your Jira API token (or OAuth 2.0 credentials) on a regular schedule, and immediately if you suspect exposure.
3. Restrict the Enterprise Admin role (which manages integrations) to a small, trusted group.
4. Prefer a dedicated service account or bot user over a personal login, so access survives staff changes.
5. Review the integration’s activity in the B6AI Activity Logs periodically for unexpected calls.
6. Disconnect the integration the moment a credential leaks; then rotate it in Jira before reconnecting.

Recommendations

1. Test against a sandbox or non-production Jira account before connecting live data.
2. Document which bots and flows depend on this integration so changes are predictable.
3. Set a recurring reminder to review scopes and rotate credentials.
4. Enable only the capabilities you actually use today; you can widen scopes later.