Use Jira with NimbleBrain.
Connect Jira and just ask — no workflow to build. Issues, JQL search, transitions, boards, and sprints. The agent gets 17 actions, running under your own credentials.
Everything the agent can do in Jira
The whole issue lifecycle rather than issue creation alone: search with JQL, read the transitions an issue is actually allowed to make, move it, assign it, and comment. Boards and sprints are readable, so the agent can answer questions about a sprint without you opening one.
17 actions
- Create issue
- Get issue
- Edit issue
- Delete issue
- Assign issue
- Transition issue
- Get transitions
- Search issues
- Search for issues using jql post
- Add comment
- List issue comments
- Get all projects
- Get issue types
- List boards
- List sprints
- Find users
- Get current user
Nobody types an action name
You ask. The agent works out which of its actions that takes, and in what order.
What is in this sprint that has not moved in five days?
Calling 1 action in Jira
- List sprints
- Working
File the bug from this support thread with the reproduction steps.
Calling 3 actions in Jira
- Create issue
- Get issue
- Edit issue
- Working
Move everything that passed review into Done.
Calling 3 actions in Jira
- Create issue
- Get issue
- Edit issue
- Working
Three steps, and Jira is reachable.
-
Install it
Find Jira in the directory inside your workspace and install it. No adapter for us to build first, no queue to join.
-
Connect the account
Sign in at the vendor, or hand an admin credential over once. Tokens stay with the workspace or the person who owns them — never pooled, never copied to us.
-
Ask for the work
The tools show up in front of the agent, under the same access wall as everything else. Describe the job in plain language, or put it on a schedule.