# Jira Cloud — an integration for Buff

> Tasks, questions and answers right in Jira Cloud tickets — without leaving the tracker your team already works in.

[Marketplace](https://buff.systems/en/marketplace) Jira Cloud

# Jira Cloud

Issue trackers · publisher buff · version 1.1.0

Tasks, questions and answers right in Jira Cloud tickets — without leaving the tracker your team already works in.

[Download the connector](https://buff.systems/en/downloads) [How to install](https://buff.systems/en/marketplace/jira-cloud#usage) 2 of 3 tools only read

- A question from a Jira ticket in the Buff interface — together with the answer.
- The setup form — each integration has its own fields: address, scope, bot name and credentials.
- The connection is live: its own set of tools and its own allowed address.
- The connection check does not just say “ok”: it reports that this is Cloud, the account it signed in with and how many projects are in scope.
- What the integration will get is written on its card in the connector’s catalogue.

Click a screenshot to open it in full. All screenshots are from a working installation.

## Overview

The integration connects Buff to your site on atlassian.net. The team keeps filing tasks and asking questions where it is used to: in the ticket. Buff reads the ticket together with its discussion, answers with a comment there and, if asked, creates a development task with a link back. The code comes from your repositories — they are connected to Buff separately, as a code source. Jira Data Center and Server have a separate integration: the cloud has a different API.

## Use cases

The situations it is installed for.

- ### A question about the code without leaving the ticket A tester has filed a ticket “CSV export breaks on Cyrillic” and does not know where to dig. They mention the bot in a comment and ask it to look into it. Result. A few minutes later the ticket holds an analysis: where the export is built, why the encoding is lost and what will have to change. Nobody created a task or switched to another interface.
- ### A development task straight from the ticket A product manager described an improvement in a ticket — with a ten-comment discussion where half the requirements appeared along the way. Result. Buff reads the whole ticket together with its comments and drafts a development task from it. The link goes back into the ticket, so the tracker stays the one place the team looks at.
- ### This happened before — find where exactly A request has come in that looks suspiciously like last year’s. Searching by hand with JQL takes a long time, and the only person who remembers it is on holiday. Result. The integration searches the selected projects and brings back related tickets: duplicates, past requests about the same subsystem and the tasks the current one depends on — with links.
- ### The answer where it is expected The person who requested the task does not open the Buff interface and has no plans to. They need an answer in the ticket they opened. Result. The finished analysis or a link to the development task arrives as a comment in the original ticket. It is the only tool of the integration that writes anything — and it is unavailable at the stages where the model only reads.

## Examples

What to write and what comes back. How the bot is addressed is set in the connection settings — here it is “@buff”.

1. @Buff, find out why Cyrillic breaks when exporting to CSV a comment in the ticket itself tool: `get_issue` I read the whole ticket together with its discussion and traced it through the code. The file is served without a BOM and with a text/csv header without a charset — Excel on Windows reads such a file as cp1251. I attached the analysis with the places in the code as a document and posted a link to it here.
2. @Buff, create a development task from this ticket a comment in the ticket tool: `get_issue` The task is created: it carries the description, the requirements that surfaced in the comments and the constraints from the discussion. The link to the task is in the reply comment, so the status is visible without leaving the tracker.
3. /research where the delay in the report comes from a comment in the ticket — this is how deep research starts tool: `get_issue` The word after the mention picks the work: without it — a short answer, “research” — deep research with a document, “task” — a draft development task. A mention inserted by the Jira editor works the same as one typed by hand.
4. @Buff, find tickets about catalogue caching a comment in any ticket of a selected project tool: `search_issues` Found 4 tickets about caching: two closed ones — about resetting the cache after a price change and warming it up after a deploy, one open about TTL and one about duplicates in results: it is similar to the current one.

## What it does

### Reads the whole ticket, not just the title

get\_issue gives the model the description and all the comments. That is what a real brief is made of: the title says “search does not work”, and the third comment says what exactly and on which data. The tool only reads.

### Searches the selected projects

search\_issues goes through the projects you selected and finds related tickets — duplicates, past requests about the same subsystem, the tasks the current one depends on. Also read only.

### Answers in the same ticket

add\_comment writes the answer to the original ticket — an analysis of the question or a link to the development task. It is the only tool of the integration that changes anything — and it is unavailable at the stages where the model only reads. The connector checks that on its side.

### Understands a document, not a string

A comment in Cloud is not text but a document: paragraphs, lists and mentions as separate nodes. The integration reads such a document and writes its answer in the same form, so a mention inserted by the Jira editor is recognised the same as one typed by hand.

### Starts work only when addressed

A board transition, a priority change or a label starts nothing: those are made by automation rules, and work nobody ordered would still be billed. Assigning a ticket to the bot’s account is a way of addressing it, but it can be automatic too, so it is turned on by a separate setting. The list of selected projects is the access control.

### Never touches your process

The integration does not move tickets across the board or change statuses, priorities and assignees. It reads and writes comments — nothing more.

## How to use it

Everything happens on the machine where the connector runs. At no step do you need to open access to your network from outside.

1. Step 1 ### Installation takes one click Open the “Marketplace” section on the connector’s local page. Before installing you can see what the integration will get: the addresses it will be able to reach, which credentials it will ask for and how many tools the model will see. The connector downloads a signed bundle from our registry and checks the signature before writing anything to disk. **Connector** ← scroll the frame → The access limits are written on the catalogue card.
2. Step 2 ### Setup: the site address, an email, a token and project keys You need the address of your site (\`https://your-company.atlassian.net\`), the email of the bot’s account and its API token from id.atlassian.com, plus the project keys — the letters before the ticket number. Cloud checks the “email + token” pair, so the form has two fields; both stay on your machine, and the integration does not see them. **Connector** ← scroll the frame → Each integration has its own form fields.
3. Step 3 ### Create a separate account for the bot Give it access only to the projects where the bot should answer: the account’s permissions are the outer boundary, and the list of selected projects is the inner one. Permission to view and comment is enough; the bot should not be a site administrator.
4. Step 4 ### Code is connected separately Jira is an issue tracker; it does not give us repositories. For the bot to answer about your code, the repositories are connected to Buff as a code source — by the same connector, in the “Repositories” section. Either works without the other: the bot can read tickets and answer in them, just without analysing the code.
5. Step 5 ### The same from the command line Installing without a GUI is an equal option, not a fallback: \`connector install jira-cloud\`, then \`connector instance add jira-cloud --config base\_url=https://acme.atlassian.net --config project\_keys=PROJ\`.
6. Step 6 ### Events arrive on their own After setup there is nothing to start: the integration watches the selected projects itself. If you want it faster, turn on event receiving in the connector and add a Jira webhook for comment events. The connector issues the link: Jira does not sign its calls, so the pass is the secret inside the link itself. **Connector** ← scroll the frame → Each connection has its own set of tools and its own allowed address.

## Access limits

The connector shows the same on your machine before installation. The list comes from the signed catalogue, not written here by hand.

Goes out to

only the addresses from the fields `base_url`

Credentials

api — the values stay in the connector, the integration does not see them

Webhooks

deliver — you open the port, if you choose to

| Tool | What it does | Access |
| --- | --- | --- |
| search\_issues | Find tickets by JQL — when a key is mentioned or context from the tracker is needed | read only |
| get\_issue | Read a whole ticket with its comments — when requirements or the discussion are needed | read only |
| add\_comment | Write a comment in a ticket | writes |

The integration runs as a separate process under its own operating system user: it does not see the connector’s key, does not read the files of other connections and cannot reach the network past the connector. More in the [security section](https://buff.systems/en/security).

## Requirements

- Jira Cloud (atlassian.net). Data Center and Server have a separate integration: the cloud has a different API.
- A bot account on the site and its API token from id.atlassian.com, with permission to view the projects needed and write comments.
- Network access from the connector’s machine to your Jira site — nothing needs to be opened from your network to the outside.
- A connector run with the right to create a separate OS user for the integration (root or CAP\_SETUID).
- For answers to be based on the code, connect the repositories to Buff as a code source — by the same connector, in the “Repositories” section.

## Questions

- **We have Jira Data Center. Will this integration work?**: No, Data Center and Server have a separate integration — in the catalogue it is called simply Jira. The cloud has a different API: a comment there is a document, not a string, and search works differently.
- **Does the API token go to your cloud?**: No. The email and the token are stored on the connector’s machine and never leave it. The integration does not see them either: the connector inserts them into the outgoing request itself.
- **Can the integration reach anything other than our Jira site?**: No. The address it is allowed to reach is derived from your own “Jira Cloud address” field, and the connector does not let a request go beyond it. What exactly is allowed is visible in the catalogue before installation.
- **Will the bot move tickets across the board?**: No. The integration reads and writes comments. Statuses, priorities and assignees stay with your team.
- **Will the bot answer a comment it wrote itself?**: No. It knows its own account and does not take its own answers for new questions.

At a glance

- **Version**: 1.1.0
- **Publisher**: buff
- **Updated**: 2026-10-05
- **Size**: 21 KB
- **Tools**: 3, 2 read only
- **Credentials**: api
- **Webhooks**: deliver
- **Platforms**: linux-x86\_64, linux-aarch64

[Connector documentation](https://buff.systems/en/docs/connector) [How it works from an information security standpoint](https://buff.systems/en/security) [Ask a question about the integration](https://buff.systems/en/contact)

On this page

- [Overview](https://buff.systems/en/marketplace/jira-cloud#overview)
- [Use cases](https://buff.systems/en/marketplace/jira-cloud#use-cases)
- [Examples](https://buff.systems/en/marketplace/jira-cloud#examples)
- [What it does](https://buff.systems/en/marketplace/jira-cloud#abilities)
- [How to use it](https://buff.systems/en/marketplace/jira-cloud#usage)
- [Access limits](https://buff.systems/en/marketplace/jira-cloud#access)
- [Requirements](https://buff.systems/en/marketplace/jira-cloud#requirements)
- [Questions](https://buff.systems/en/marketplace/jira-cloud#faq)

Next

## Connect Jira Cloud

Install the connector in your network, open its local page and install the integration from the catalogue. Nothing needs to be rebuilt.

[Download the connector](https://buff.systems/app) [Write to us](mailto:info@buff.systems)

Companies and sole traders can pay by bank transfer and receive closing documents