Integration · Projects and tasks
AI agents for Jira
Create, search, comment on and move Jira Cloud issues on your Atlassian site, signed in with an email address and an API token.
- Actions
- 5
- Read
- 2
- Write
- 3
Actions
What your agents can do in Jira
5 actions. Each one is a tool your agents can call and a step your workflows can run.
Read 2
Look things up. Nothing changes.
Get an issue
Reads one Jira issue by its key or ID: summary, status, assignee, reporter, priority, type, labels, dates and description.
Search issues with JQL
Finds Jira issues with a JQL query, like project = PROJ AND status != Done ORDER BY updated DESC.
Write 3
Create, change or send.
Create an issue
Creates an issue in a Jira project: a bug, task, story or any issue type the project has, by its name.
Comment on an issue
Adds a plain-text comment to a Jira issue, by its key or ID.
Transition an issue
Moves a Jira issue through its workflow, for example from To Do to In Progress or Done, by a transition ID.
A person can approve first
Any write action can be set to wait for a person's approval before it runs, so an agent asks before it changes anything.
Connection
How it connects
Connect it once in the console, then give it to the agents and workflows that need it.
Enter the API credentials from your Jira account.
What you enter
- Email address
- API token
Settings
- Site name
Kept safe
- Credentials are stored encrypted with your organization's own keys.
- They are opened only by the process that makes the call, at the moment it runs, and never go into a prompt or the browser.
- Calls go only to the tool's own servers.
Ideas
Ideas to start with
Starting points made only from the actions above. Mix them with any other tool your agents can use.
- 01
Ask about your Jira data
Ask a question in plain words. The agent can get an issue or search issues with JQL in Jira, then answers with what it found.
- 02
Let an agent update Jira
Have the agent create an issue or comment on an issue in Jira as part of a larger task. Turn on approval and a person signs off on each change first.
- 03
Share what it finds in Slack
Give one agent Jira and Slack: it can get an issue in Jira and post a summary to a Slack channel in the same run.
Works well with
More Projects and tasks tools
- Asana5 actionsCreate, read, update and complete Asana tasks and comment on them, in the workspaces a personal access token can reach.
- Linear5 actionsCreate, find and comment on Linear issues in the teams a personal API key can reach.
- Trello4 actionsCreate Trello cards, comment on them and move them between lists, on the boards your Trello account can reach.
- ClickUp4 actionsCreate, read and update ClickUp tasks and comment on them, in the Workspaces a personal API token can reach.
- monday.com3 actionsCreate items on monday.com boards, post updates on them, and read items with their column values, with a personal API token.
- Aha!16 actionsFind, read, create and update Aha! features and ideas (status, assignee, dates), comment on them, log time on features, write notes, and look up workspaces, releases and users in an Aha! account.
FAQ
Jira and MyDeepAgents
Can MyDeepAgents connect to Jira?
Yes. The Jira connector has 5 actions: 2 read and 3 make changes. Your agents can call them as tools, and your workflows can run them as steps.
How do I connect Jira?
Enter the API credentials from your Jira account. You'll need: Email address and API token. The connection also asks for: Site name. Credentials are stored encrypted with your organization's own keys and are opened only at the moment of a call.
Can an agent change data in Jira without asking?
Only if you let it. Each of the 3 actions that change data can be set to wait for a person's approval before it runs.
Can I use Jira in workflows as well as agents?
Yes. Every Jira action also works as a step in a workflow, and the same connection serves your agents and your workflows.
Early access
Put Jira to work
Connect it in a few minutes, give an agent the actions it needs, and decide which changes wait for a person.