Jira
Jira connects issue work to Mobius.
A Jira integration connects an Atlassian Cloud site to Mobius. It lets assistants inspect and update Jira issues. It can also receive Jira issue and comment events.
Use Jira when work intake or remediation lives in Jira and the assistant needs to write back status, comments, assignments, worklogs, links, or transitions.
Capability map
| Capability | Value |
|---|---|
| Provider ID | jira |
| Auth kind | api_key |
| Connect flow | Inline Atlassian email and API token |
| Actions | Yes |
| Events | Yes |
| Webhook delivery | Yes |
| Event samples | No |
| Live status | No |
Connect Jira
| Surface | Support |
|---|---|
| App | Open Build > Integrations, choose Jira, and provide the site URL, email, API token, and optional defaults. |
| CLI | The mobius CLI does not connect Jira integrations yet. Use the app or API. |
| API | Call POST /v1/integrations/providers/jira/connect through the generic provider connect endpoint. |
Jira webhook delivery uses a provider webhook URL for the organization. Keep the webhook secret in the integration config so Mobius can verify deliveries before turning them into source events.
Jira is a team-managed workspace connection. An organization administrator connects it, and Jira API calls act as the Atlassian user named by the saved email and API token. The site URL and that user determine which projects and issues Mobius can reach.
Open the connected account and use Assistant access to grant this exact site to the assistants that need it. Choose the whole team or named people as its Mobius result audience. The grant applies in conversations and routines; a routine also saves the exact Jira connection it will use.
Actions
jira.issue.add_comment
jira.issue.add_watcher
jira.issue.add_worklog
jira.issue.assign
jira.issue.create
jira.issue.create_link
jira.issue.delete_comment
jira.issue.delete_link
jira.issue.get
jira.issue.get_changelog
jira.issue.get_comments
jira.issue.get_worklogs
jira.issue.search
jira.issue.transition
jira.issue.update
jira.issue.update_comment
jira.issue_link_type.list
jira.issue_type.list
jira.label.list
jira.priority.list
jira.project.get
jira.project.list
jira.user.searchUse jira.issue.search before mutating actions when the assistant receives loose
input, such as a human-written ticket key or component name. Transition actions
need a valid transition for the current issue state.
Jira mutations, including creating or updating an issue, adding a comment, assigning work, logging time, changing a transition, or deleting a comment or link, run without an automatic Mobius confirmation. Dispatch still rechecks the exact Jira connection and assistant grant.
Events
jira.comment.created
jira.comment.updated
jira.issue.created
jira.issue.deleted
jira.issue.updatedUse jira.issue.created for intake and jira.issue.updated for state changes.
Use comment events when the assistant should respond to human discussion instead of
every field update.
Next
- Review account access in Connect accounts.
- Give the assistant safe bounds with guardrails.
- Inspect actions from actions.
- Review event names in the event catalog.