Time: about 15 minutes · Role: Admin on Enterprise; Admin or Member on SaaS · Works on: Enterprise and SaaS. On SaaS, adding a toolkit needs an active subscription with spending room left. · You need: a Jira Cloud site, an account on it and an API token for that account, and an agent you can edit (for example the one from Build your first agent)
- Enterprise: Admins only. A Member uses the toolkits an Admin has shared with them, so ask an Admin to do stages 1 and 2 and share the toolkit with you. Viewers have no Toolkits page.
- SaaS: Admins and Members. A toolkit a Member adds can be used by them and the Admins, unless they make it public.
What you will have at the end
- A toolkit named “Jira - Support” with the status Active.
- The agent able to use the Jira tools you chose.
- A finished task in which the agent read issues from your Jira.
1. Connect Jira
The agent acts in Jira as the account whose token you enter. It sees what that Jira user may see, so use an account with the access the agent should have.1
Open Add Toolkit
In the sidebar, under Integrations, click Toolkits, then Add Toolkit. Under Productivity & Collaboration, click Jira.
2
Name it
Under Basic Information, change the Toolkit Name to “Jira - Support”. The name must be unique and cannot be changed later.
3
Enter the credentials
Under Credentials, fill in:
- Jira URL: your site’s address, such as
https://your-company.atlassian.net. - Username / Email: the email of the Jira account.
- API Token: the token you created for that account in your Atlassian account settings.
4
Test the connection
Click Test Connection.
A green Connection Successful box says how many tools it found.
2. Choose who may use it, and save
1
Set the visibility
Under Access Control, leave Visibility on the private option while you try it out. Choose Public - All organization members can use later, when colleagues should add it to their own agents. A SaaS personal account has no such section: the toolkit is yours.
2
Create it
Click Create Toolkit. Neural Factory reads the list of Jira tools and you return to Toolkits.
”Jira - Support” is in the list with the status Active.
3. Give the toolkit to the agent
Only the agent’s creator and Admins can change it.1
Open the agent
Under Workforce, click Agents, then click the agent. It opens in the studio.
2
Add the toolkit
Click Edit on What it can do. Under External Toolkits, open Search and select toolkits… and pick “Jira - Support”. All its tools are selected.
3
Untick what the agent should not do
For an agent that only reads, untick the tools that create, update, assign or delete issues. Click Save changes.
4
Publish
Click Publish in the header, then Publish in the dialog. Until you publish, tasks keep using the earlier revision without Jira.
What it can do lists “Jira - Support” with the tools you kept.
4. Run a task that uses Jira
1
Start a task
Click New task and pick the agent in the composer’s bar.
2
Ask about your issues
Name a project your Jira account can see. For example: “List the five most recently updated open issues in project SUP, with their status and assignee.” Press Enter.
3
See what the agent did
Click the monitor button in the top bar, or press ⌘L / Ctrl+L. The Execution Trace panel lists each step, including the calls the agent made to Jira.
The answer lists real issues from your project, and the trace shows the Jira tool calls.
If something goes wrong
- Connection Failed: the box says why. Check the Jira URL (with
https://), the email and the token, then test again. If you create the toolkit anyway, you are asked Save Toolkit Anyway? and can fix it later with Configure in the row’s menu. - The toolkit is not offered in the agent: you can only pick toolkits you have access to. Ask the Admin who added it to make it public or share it with you.
- The agent says it cannot find the project or an issue: the Jira account behind the token may not see it. Check that account’s permissions in Jira.
- The toolkit shows Error: open it to read the reason, fix the credentials with Configure, or choose Refresh Tools. See Connection problems.
Where to go next
- External integrations: what Jira and the other toolkits can do
- Managing connections
- Start from the Catalogue