Productivity
AI agents that use Jira
UtilitySpaces gives an AI agent scoped access to Jira through its own encrypted connection, not your password. The agent can call 5 named Jira tools, and the 2 that write wait for a person's approval unless an admin has set the connection to run without asking. Every call is written to a hash-chained audit log with its arguments and its result.
What an agent can do in Jira
Search, read, create, and comment on issues in a Jira Cloud site. An agent calls these by name, and matching is exact.
| Tool | What it does | Waits for approval by default |
|---|---|---|
| Get myself | Get the token's own user (cheap token check). | No — read only |
| Search issues | Search issues with a JQL query. | No — read only |
| Get issue | Get an issue by key or id. | No — read only |
| Create issue | Create an issue from a fields object. | Yes — it writes |
| Add comment | Add a comment to an issue (Atlassian Document Format body). | Yes — it writes |
3 read tools, 2 write tools. Generated from the connector catalogue the product runs on, so it cannot list a tool that does not exist.
What teams hand an agent in Jira
Engineering teams hand an agent the JQL they would type: Search issues for what is open in a sprint, assigned to one person, or untouched for a week, then Get issue for the detail. Create issue and Add comment are the writes, and both wait for a person to approve them unless an admin has set this connection to run writes without asking.
- Answer "what is blocked" in the inbox by running a JQL search for the sprint and summarising the issues by assignee.
- Create an issue when a bug report in chat or a support ticket has enough detail to reproduce (once someone approves it)
- Add a comment to an issue when related context lands elsewhere, such as a reporter's follow-up message (after a person approves it)
What waits for a person
Reads run on their own. These do not — each one waits in Approvals for an owner or admin unless an admin has set this connection to run writes without asking, and every call toJira, approved, rejected or unattended, is logged.
- Create issue POST
- Add comment POST
What connecting Jira takes
Jira uses an API key you create in Jira and paste in once. A workspace admin sets the connection up; the fields are:
- Site URL
- Account Email
- API Token
Credentials are encrypted and bound to your workspace, never read back, and every outbound call passes one guarded fetch — the connector security posture sets out exactly how, and the security page covers the platform around it.
Where Jira fits
Give an agent Jira work by writing a message in the inbox, or put its tools in a scheduled flow. What the run cost is on the cost breakdown.
Other productivity integrations: Airtable, Asana, Calendly. Or see every application agents can connect to.
See it doing your actual work
Open a demo workspace, connect one app, and give an agent a real job. No card, no sales call.
We reply to every message within one business day.