openai / openai/codex

Feature request: Upload Jira attachments through Codex integration

Open
#42,525 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

app enhancement tool-calls
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

What variant of Codex are you using?

App

What feature would you like to see?

Please add attachment-upload support to Codex's direct Jira integration.

Current workflow:

  • Codex can create, read, and edit Jira issues through the integration.
  • The available Jira tools do not include an attachment-upload action.
  • When a task requires attaching a Slack screenshot to a Jira issue description, the agent must fall back to browser UI automation and a local download.

Requested capability:

  • Add a Jira attachment-upload tool/API that accepts a local file or conversation image.
  • Allow inserting the uploaded image directly into Jira description and comment fields when supported.
  • Return attachment metadata or a link so the agent can verify the upload.

This would keep Jira workflows within the direct integration, eliminate manual browser steps, and reliably preserve important visual context.

Additional information

Observed in the Codex desktop app while creating and updating Jira work items.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating Codex's direct Jira integration and the existing Jira issue creation, reading, and editing tools. Review how those tools handle local or conversation-provided content; done means an attachment can be uploaded, inserted into supported descriptions or comments, and its metadata or link is returned for verification.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
api, backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.