Smart Fusion

AI Developer

Integration of Claude Code / OpenAI Codex

AI Developer is your autonomous AI engineer powered by Claude Code / OpenAI Codex inside Jira. It takes over issues directly from your backlog, analyzes the task, and delivers working results within minutes. Whether it'prototyping new features, resolving bugs, or accelerating delivery, AI Developer transforms ideas into reality without disrupting your existing workflow.

With AI Developer, your team gains the ability to prototype faster, code smarter, and remove bottlenecks from the development process.

When assigned to an issue, AI Developer generates a solution, pushes the implementation to a dedicated Git branch and shares the outcome as a comment in Jira - ensuring transparency and keeping the team in control. Each assignment runs in a secure, isolated environment to protect your code and maintain full data integrity.


AI Developer

An autonomous AI engineer, powered by Claude Code / OpenAI Codex, that runs inside Jira. Assign any issue and it will analyze the task, generate a solution, and deliver working code — typically within minutes.

How it works

You assign issue
AI analyzes task
AI generates solution
Code pushed to branch
Comment posted on issue

What AI Developer does

  • Reads the issue summary and description
  • Generates a solution — code, tests, and dev notes as applicable
  • Pushes the implementation to a dedicated Git branch
  • Posts a comment on the Jira issue with the outcome

Works best for clearly scoped tasks: prototyping features, resolving bugs, or accelerating delivery without disrupting your workflow.

Features

Assign to AI Developer button

Added to every Jira issue page. One click hands the issue to the AI.

Automatic solution generation

Generates a complete proposed solution — code, tests, and dev notes — directly from the issue summary and description.

Git integration

Commits changes and pushes to a dedicated branch in your configured repository.

Jira visibility

A comment is created on the issue with the solution summary and branch name for full transparency.

Configuration

You need three things before AI Developer can push code: an HTTPS Git connection, a repository access token, and a Claude/Codex API key.

App setup

  1. Open Project / Space Settings → Apps → AI Developer
  2. Enter your HTTPS repository URL, e.g. https://github.com/your-org/repo.git
  3. Enter the base branch to start from, e.g. main
  4. Enter your Git username and access token as the password (see token guides below)
  5. Optionally set an identifier to differentiate multiple repositories
  6. Choose your AI connection method and enter the relevant credentials (see below)

AI connection

You can use AI directly from the AI Provider Anthropic/OpenAI or use it via AWS Bedrock or Microsoft Foundry (only supported by now by the "Integration of Claude Code"; availability for "Integration of OpenAI Codex" with the next release).

Create a Claude API key / Codex API Keyand paste it into the LLM API Key field.

Git access tokens

Use a Personal Access Token (PAT). Fine-grained tokens are recommended for tightest control.

  1. Go to Settings → Developer settings → Personal access tokens → Fine-grained tokens
  2. Click Generate new token, give it a name, and set an expiry date
  3. Under Repository access, select only the repositories AI Developer should act on
  4. Set permissions: Contents read & write · Commit statuses read & write · Pull requests read & write (if you want PRs created)
  5. Generate the token, copy it, and paste it as the HTTPS password in Jira settings

Usage

After installation, an Assign to AI Developer button appears in the context panel of every issue. Click it to send the issue to the AI for resolution.

Writing effective issues

AI Developer has no project memory — everything it needs regarding requirements must be in the issue description. Well-written issues produce significantly better results.

Include in the description
  • Business requirements — goals, acceptance criteria, inputs/outputs, constraints
  • Technical context relevant to this specific task
  • Expected vs. current behavior (for bugs)
Structure tips
  • Use bullet points or numbered lists for clarity
  • Separate technical details from business requirements
  • Break large tasks into multiple smaller issues

If the first result isn't right, refine the issue description — add more context, rephrase, or restructure — and re-assign.

Support

For help or to report issues with the plugin, email support@smart-fusion.tech.

Security tips

Use service accounts

Prefer machine or service accounts for tokens rather than personal user accounts.

Set expiry and rotate regularly

Always set an expiration date when creating tokens and rotate them periodically.

Apply least privilege

Restrict tokens to the minimal set of repositories and scopes required. Use fine-grained tokens where supported.