Integrations · Projects & issues

Jira in the conversation.

Atlassian's issue tracker, and the queue engineering actually works from. Connect it once and your copilot works with issues, projects, sprints, comments and transitions without leaving the thread — and your workflows can act on it while the customer is still typing.

Start free trial →All integrations

No credit card required · 7-day free trial

Jira

Projects & issues

01 · COPILOT

Ask for it in plain language. It does the Jira part.

Copilot rides inside the inbox. With Jira connected it reads issues, projects, sprints, comments and transitions and acts on them from the same panel as the conversation — no second tab, no copying an order number across.

Search issues with a JQL-shaped query
Read an issue, its status and its comments
Create an issue in a project with the right type
Comment on an issue
Transition an issue or change its assignee and priority
Attach a file or a transcript to an issue

What a specific connection exposes is decided by Jira, not by us: Settings → Apps lists the real tools your connection carries, each with its own switch.

02 · WORKFLOWS

Something happens in Jira. A workflow starts.

Once Jira is connected, its events show up in the workflow editor's trigger picker, and the fields the event carries become variables every later step can read — so the message you send is written from what actually happened.

An issue is created
An issue transitions status
A comment is added

The picker is the authority on which events your Jira connection publishes — these are the kinds that apps of this sort emit.

03 · THE AI AGENT STEP

One step that decides which Jira tools to call.

A workflow's AI Agent step runs a bounded tool-calling loop over the apps you have connected and returns an object whose fields you declared. So "find the record, check the status, and give me status and owner" is one step rather than four — and the fields it returns are available to every step after it.

You declare the output

The rows you name become the variables downstream steps read, so a branch can test what Jira said.

You cap the effort

A step budget and a model tier per node — the loop stops where you told it to.

Only what you switched on

The loop can call the Jira tools you left enabled and nothing else.

What teams do with it

Two ways Jira earns its connection.

A bug report with the evidence attached

The conversation that found the bug becomes a Jira issue with the transcript, the customer and the channel already on it.

Tell the customer when it ships

A workflow fires when the issue moves to Done and reopens the original conversation to tell the person who reported it.

Setup

Connect Jira in about a minute.

1
Open Settings → Apps
It is open to everyone in your organization, not just admins — which apps your copilot can reach is part of doing the job.
2
Find Jira in Browse
The catalogue runs to hundreds of apps and is searchable. Connect Jira from its card.
3
Authorize with your own Jira account
You sign in on Jira's own screen and approve the access. The connection carries that account's permissions — no API keys are pasted into Cloodot.
4
Choose the tools it may call
Open the connection and switch off anything you would rather it never touched. A tool you switch off is out of reach from the next question onward.

Open Settings → Apps →

Jira questions.

How do I connect Jira to Cloodot?

Open Settings → Apps in Cloodot, switch to Browse, and search for Jira. Connecting it opens Jira's own sign-in and consent screen; when you come back, the app is listed as Connected and your copilot can use it. Nothing is installed and no keys are pasted into Cloodot.

What can Cloodot do in Jira?

Work of this kind: search issues with a jql-shaped query; read an issue, its status and its comments; create an issue in a project with the right type; comment on an issue; transition an issue or change its assignee and priority; attach a file or a transcript to an issue. The exact list depends on what your Jira account is allowed to do — Settings → Apps shows every tool the connection actually exposes.

Can I limit which Jira tools Cloodot may use?

Yes. Open the connection and every tool it exposes is a switch, searchable by name. A tool you switch off is out of reach from the next question onward, so a read-only Jira connection is a matter of leaving the writes off.

Can an event in Jira start a Cloodot workflow?

Yes. Events like an issue is created, an issue transitions status, a comment is added appear in the workflow editor's trigger picker once Jira is connected, and the event's own fields become variables the rest of the workflow can read.

Who in my team can connect Jira?

Anyone in the organization — Apps is not restricted to admins and owners, because which apps a copilot can reach is part of doing the job. The connection carries the permissions of the Jira account that authorized it, so a projects & issues connection is only ever as broad as the account behind it.

More projects & issues