Connect Codex to Jira
Give your Codex agent access to Jira in Melso — 97 tools it can call while it works through a task.
Set it up in Melso
- 1In Melso, open Settings → Agent Apps and hit Connect on Jira.
- 2Finish the OAUTH2 / S2S_OAUTH2 sign-in in the window that opens. Melso stores the connection, not your credentials.
- 3Open your Codex agent, go to its Agent Apps tab, and allow Jira.
- 4Give the agent a task. It calls Jira itself when the work needs it.
What Jira gives your agent
The tools, permissions, and events Jira exposes — the same ones your agent can use once the app is authorized.
What you sign in with
Jira connects with OAUTH2 / S2S_OAUTH2.
- Client id
- Client secret
Permissions
Tools Jira exposes
Add Attachment
Uploads and attaches a file to a Jira issue.
Add Comment
Adds a comment using Atlassian Document Format (ADF) for rich text to an existing Jira issue.
Add Users to Project Role
Adds users and optionally groups to a project role.
Add User to Group
Adds a user to a Jira group.
Add Watcher to Issue
Adds a user to an issue's watcher list by account ID. Requires the authenticated user to have permission to view the issue and manage watchers; insufficient permissions may result in silent failure or an error response.
Add Worklog
Tool to add a worklog entry to a Jira issue. Use when logging time spent on an issue.
Analyse Jira Expression
Analyses Jira expressions for syntax validation, type checking, and complexity analysis. Use when you need to validate Jira expression syntax before using it in automation rules, custom fields, or workflows.
Assign Issue
Assigns a Jira issue to a user, default assignee, or unassigns; supports email/name lookup.
Events your agent can react to
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
New Project
Triggered when a new project is added in Jira
Updated Issue
Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.