Coding agent · Jira and GitHub

From Jira ticket
to pull request.

The coding agent reads a Jira ticket, writes the change in your GitHub repositories and opens a pull request. It can run your tests first. Nothing is merged until you approve it.

On InAgentic servers it uses an open-source coding model on your server (Qwen3 Coder 30B).

One change, start to finishexample
Ticket
ABC-12 · Fix the signup form
Repositories
2
Files changed
5
Tests
Run before the pull request
Pull requests
2 · awaiting approval
Merged by
You, on Approve
Jiratickets in
GitHubpull requests out
0merges without your approval
10repositories in one change

Small tickets pile up.

Routine fixes and small features wait in the backlog because nobody has an afternoon to pick them up, review them and ship them.

  • Small tickets wait weeks for a developer
  • Context switching costs more than the change
  • Changes across several repos are easy to get out of step
  • Every change still needs a careful review

Tickets in, reviewed pull requests out.

🎫

Jira

  • Lists your recent tickets
  • Reads a ticket in full
  • Creates tickets (Task, Bug, Story) when you ask
  • Jira Cloud
🔀

GitHub

  • One branch per change
  • One pull request per repository
  • Up to 10 repositories in one change
  • Closes what it opened if a step fails
🧪

Checks

  • Runs your tests before the pull request
  • Live preview: click through the next version before the pull request
  • Before and after screenshots, if your repo has a screenshot command
  • Rebuild with your feedback
✅

Approvals

  • Approve merges the pull request
  • Reject with a reason the agent sees
  • Approve all checks every repo first
  • Merged on GitHub? It notices
📘

Your rules

  • Your instructions for the agent
  • Reads AGENTS.md or CLAUDE.md in each repo
  • Only the repositories you allow
🛡️

Limits

  • Can’t change .github/workflows or .git
  • No merge or deploy tool
  • No binary files
  • Every step in the audit log

Ask in the chat or Slack. Approve when you’re happy.

01 · ASK

“Build ticket ABC-12”

Ask in the chat or in Slack. The agent reads the ticket and your instructions.

02 · WRITE

It writes the change

In a clean checkout of your default branch, with the files it needs.

03 · CHECK

Tests run

Your setup and tests run before anything reaches GitHub.

04 · APPROVE

You decide

Review the diff, screenshots or the live preview. Approve to merge, reject with a reason, or ask for a rebuild.

On the Pull requests page you see what is waiting, the diff, screenshots, live previews and your approval rate.

From the chat or Slack to the review page.

💬

Chat

“Build ticket ABC-12”, “List my last 5 Jira tickets”, “What’s waiting for my approval?”. Hermes calls the coding agent for you.

#️⃣

Slack

Ask for a build from Slack, e.g. “Build ticket ABC-12”.

📋

Pull requests page

Waiting changes, before and after screenshots, the diff, and Approve, Reject or Revise.

📁

Repositories page

Add repositories and GitHub tokens, write instructions for the agent.

⚙️

Model & tools

Choose the engine and whether tests run before the pull request.

Your code and your keys.

What it needs

A GitHub fine-grained token (contents and pull requests, read and write) for the repositories you allow, and your Jira address, email and API token.

Where keys are kept

Encrypted on your server, shown only by their last 4 characters. Token expiry is tracked and you’re warned 7 days before.

Where code is processed

With the default open-source model, on your server: ticket text and code go only to GitHub and Jira. If you choose OpenRouter with your own key, they’re also sent to that provider.

What stays

Screenshots stay on your server and are never committed. Nothing is merged or deployed by the agent itself.

Not there yet.

Planned, partly built or not yet set up on InAgentic servers. We'll say so here until it works.

🔁

Resume after a restart

Coming

A change being written when the server restarts is marked failed; ask again to restart it.

🧰

Other trackers and Git hosts

Coming

Jira Cloud and GitHub only for now.

Questions people ask.

Can it merge on its own?

No. It has no merge tool. A pull request is merged only when an admin clicks Approve (or someone merges it on GitHub).

Which model writes the code?

On InAgentic servers, an open-source coding model on your server (Qwen3 Coder 30B). You can switch to OpenRouter with your own key on Model & tools.

How big can a change be?

Up to 10 repositories and 150 files in one change, 50 files per repository, 500 KB per file.

Can it change our CI?

No. Files under .github/workflows and .git are blocked, and it only writes to repositories you’ve allowed.

Who do I contact?

Your team's administrator, or INAGENTIC LTD at axel@inagentic.ai.

Coding agent — Jira tickets to GitHub pull requests · InAgentic