Fix a ticket: tracker to pull request
Give the agent a ticket and it runs the whole cycle: read the ticket, find the code, reproduce the defect, fix it, run the checks, commit, push, open the pull request and update the ticket. The steps that others can see wait for your approval.
Beta Works in the Ingot agent chat and as a Rex mission, with Jira, Asana, OpenText Octane, Linear and GitHub Issues, on GitHub, GitLab, Bitbucket, Azure DevOps and Gitea / Forgejo.
Start
In the agent chat, any of these:
- Type
fix PROJ-123(orfix #12for a GitHub issue). - Paste a ticket URL from Jira, Asana, Octane, Linear or GitHub.
- Type
/fix-ticket PROJ-123. - Open the
{ + }menu and pick Fix a ticket. With no key, the agent lists your open defects from the connected trackers and asks which one to fix.
A question such as "why did PROJ-12 break?" stays an ordinary message.
What the agent does
| Step | What happens | Asks first |
|---|---|---|
| Read | The ticket, its comments and what the tracker returns about links and attachments | No (reads only) |
| Branch | fix/PROJ-123-short-summary, created before any edit | Your git approval setting |
| Reproduce | A test that fails because of the defect, run once to see it fail | Your command approval setting |
| Fix and check | Small edits, then the failing test and the project's checks again | Your command approval setting |
| Commit | The subject starts with the key: PROJ-123: …. Ingot adds the key if the model left it out | Your git approval setting |
| Push | The ticket branch only, never main, master or a release branch | Yes |
| Pull request | Title with the key; the body links the ticket and lists the checks that ran | Yes, every time |
| Ticket | A comment with the pull request link, then the move to In Review | Yes, each write |
Skip a step on its card and the agent stops there and says what is left.
Pull requests on every host
The agent opens the pull request with one tool, open_pull_request:
- GitHub: with the GitHub sign-in Ingot already has (the GitHub CLI,
GH_TOKEN, or the GitHub MCP server's token). - GitLab, Bitbucket, Azure DevOps, Gitea / Forgejo: with the account you connected in Git Hosts.
When the host is not connected, nothing is opened and the agent gives you the host's "new pull request" page instead.
Connect your tracker
Trackers are MCP servers. Connect one on the Rules & MCP page:
| Tracker | How it connects |
|---|---|
| Jira | Jira & Confluence: one-click sign-in with your Atlassian account |
| Asana | Asana: sign-in through an Asana app. Asana does not let apps register themselves, so you enter the client ID of an app you created in the Asana developer console |
| OpenText Octane | OpenText Octane: your own server URL, https://<your-octane-host>/mcp. An Octane admin must turn MCP on for your site and register the client or give you an API token |
| Linear | Linear: one-click sign-in or an API key |
| GitHub Issues | GitHub: your GitHub sign-in |
Without a connection the agent asks you to paste the ticket text and leaves the ticket alone at the end.
What the agent can do on a ticket depends on the tools the tracker's server offers. If a server has no tool for a step (for example, a status change), the agent says so instead of guessing.
Rex
In Rex, start a task on a connected repo with Fix ticket PROJ-123 or a ticket link. It runs as a mission:
- Rex reads the ticket with the connected app, reproduces and fixes the defect.
- The platform commits on
ingot-bot/fix-PROJ-123-…, with the key in the commit subject and the pull request title, and links the ticket at the top of the pull request. - After the pull request is open, Rex comments on the ticket and moves it to In Review. Each change waits on the approval card.
Turn it off in Rex › Settings › Missions: Fix tickets and Update the ticket after the pull request.
Settings
| Setting | Default | What it does |
|---|---|---|
ingot.tickets.fix.enabled | true | Fix ticket, and the agent's open_pull_request tool (Settings › Features) |
ingot.tickets.fix.detect | true | Start on fix <key> or a pasted ticket URL. Off: only /fix-ticket and the { + } action |
ingot.tickets.fix.branchPrefix | fix/ | What ticket branches start with |
ingot.tickets.fix.comment | true | Comment on the ticket after the pull request opens |
ingot.tickets.fix.moveTo | In Review | The status to move the ticket to. Empty: leave it |
ingot.tickets.fix.draftPullRequest | false | Open ticket pull requests as drafts |
They are under Settings › Version Control › Tickets, and a project can set them in .ingot/settings.json.
Limits
- Attachments are read only as far as the tracker's server returns them.
- Octane documents read tools; whether a comment or a phase change is possible depends on your site's server.
- Rex opens pull requests on GitHub and GitLab. On other hosts the change stays in the run log.
- Commits and pull requests carry the attribution unless you turn it off.