Jira
Connect Jira when your organization wants Jira delivery work available to Eos conversations, records, and Agents. The integration supports optional automatic imports into Eos as well as skills that read and change Jira directly.
You can use Jira skills while webhook imports are off. The checkbox controls automatic copies in Eos; it does not control direct skill access.
Connect Jira
You need permission to manage organization integrations in Eos and permission to authorize the Jira site.
- Open Integrations.
- If Jira is not available, open Enable/Disable Integrations and enable it for your organization.
- Open Org Connections, find Jira, and choose Connect.
- Sign in to Atlassian, choose the intended Jira site, and approve access.
- Return to Eos and confirm that the connected tile shows the expected Jira site name and address.
The connection belongs to the active Eos organization. Disconnecting stops Jira skills and future imports but does not delete records already copied into Eos.
Enable Automatic Imports
Select Enable webhook imports for this org on the connected Jira tile. Review the confirmation window, then choose Enable webhook imports.
When enabled, Eos imports:
- Jira projects as Eos projects
- Jira issues as Eos tasks
- Jira comments as Eos discussion entries linked to the imported task
- Jira worklogs as Eos time logged
- Jira sprints as Eos sprints
Changes normally appear in Eos within a few minutes. Eos stores the Jira identity on imported records so subsequent Jira changes update the same Eos record rather than create a duplicate.
What The Webhook Does
The webhook is a one-way automatic import from Jira to Eos. It does not send Eos changes back to Jira.
Jira notifies Eos about issue, comment, and sprint activity. Worklogs are refreshed when Eos processes the related issue activity, so a worklog may arrive together with the issue refresh rather than as an independent notification.
Turning the checkbox off stops future automatic imports and removes the organization’s Jira webhook registration. It does not disconnect Jira, disable Jira skills, or remove records already imported.
Use Jira Skills Without Copying Data Into Eos
Jira skills work directly with the connected Jira site. This is useful for questions, reports, and provider-side actions that do not need a permanent Eos copy.
From Eos Chat, you can ask for work such as:
- “Show overdue Jira issues for the DELIVERY project.”
- “Run this JQL query and summarize the result by status.”
- “Create a Jira issue for this approved Eos task.”
- “Assign this Jira issue and move it to In Progress.”
- “Add this update as a Jira comment.”
- “List the sprint backlog and unassigned issues.”
- “Log two hours of work against this Jira issue.”
Available skills cover projects, issues, fields, issue types, users, comments, boards, backlogs, sprints, transitions, and worklogs. They can search and summarize Jira, create and update issues, assign or transition work, add comments, move issues into sprints, and create, update, or delete worklogs.
A read skill can display Jira data in the conversation without saving it in Eos. If you want an Eos copy, ask Eos to create or update the corresponding project, task, discussion entry, sprint, or time entry using the retrieved data and preserve its Jira identity.
Skills that write to Jira change the connected Jira site even when webhook imports are off. Review the target project, issue, sprint, user, and worklog before confirming a write.
Use Jira In An Agent
Agents can combine Jira skills with Eos skills to create organization-specific workflows. For example, an Agent can:
- report on overdue or unassigned Jira work without copying it into Eos
- import only a selected Jira project or JQL result into Eos
- create a Jira issue after an Eos approval
- create or update Eos tasks from Jira and preserve their external identities
- compare Jira worklogs with Eos time or project forecasts
- summarize a sprint and create follow-up work in either system
Write the Agent intent so the direction is unambiguous. Say whether it should read Jira, write Jira, update Eos, or combine those actions. If both systems can change the same business field, define which one is authoritative.
Before making an Agent active, build it, review the interpretation, and simulate it with a narrow project or JQL filter. Jira searches can cover large amounts of work, so use explicit projects, dates, statuses, or issue types for scheduled runs. See Agents.
Avoid Duplicate Or Circular Updates
The automatic importer uses Jira identities to update existing Eos records. A custom Agent that copies Jira work should also update linked records rather than create a new task or time entry on every run.
If the webhook imports Jira into Eos and an Agent pushes Eos changes back to Jira, limit the outbound action to deliberate changes or approved fields. Otherwise, the same change can travel through both systems unnecessarily.
Troubleshooting
- If Connect is unavailable, confirm that Jira is enabled and that you can manage organization integrations.
- If the wrong site is shown, disconnect and reconnect to the intended Atlassian site.
- If automatic changes do not appear, confirm the webhook checkbox is on and the tile does not show Needs attention.
- If only a worklog seems delayed, allow the related issue refresh to complete.
- If a skill cannot see a project or issue, confirm that the Atlassian account used for the organization connection can access it.
- If a scheduled Agent returns too much data, narrow its Jira project, JQL, date range, or status conditions.