Code and issues
Jira
A Jira integration connects an Atlassian Cloud site to Mobius so loops can create, update, transition, and inspect Jira issues while reacting to Jira issue and comment events.
Use Jira when work intake or remediation lives in Jira and the run 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 Govern > 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/projects/{project}/integrations/providers/jira/connect through the generic provider connect endpoint. |
Jira webhook delivery uses a provider webhook URL for the project. Keep the webhook secret in the integration config so Mobius can verify deliveries before turning them into source events.
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 loop receives loose
input, such as a human-written ticket key or component name. Transition actions
need a valid transition for the current issue state.
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-driven
loops. Use comment events when the agent should respond to human discussion
instead of every field update.
Next
- Give the loop safe bounds with guardrails.
- Inspect actions from actions.
- Review event names in the event catalog.