Integrations

RepoHelpdesk for Jira

Ask RepoHelpdesk about the code behind a ticket — and get an answer in plain English, right inside the issue. No tab-switching, no pinging engineering.

Free on every plan. There's no add-on and no tier gate. What the integration does need is a running Agent paired to the project that owns the repos behind your tickets. Set that up first in Install the Agent and Connect your repos.

What you get
How it works
Install the app
Ask about a ticket
What RepoHelpdesk can see
Permissions and roles
Troubleshooting

What you get

RepoHelpdesk adds a panel to your Jira issues. When a customer bug or question lands in a ticket, your support engineer asks RepoHelpdesk about it from the issue itself — and gets an answer sourced from the actual code that ships, with the file and line it came from.

No new tab. No "let me check with engineering." The ticket is the context; the answer arrives where the work already happens.

Add epic / KAN-3

Checkout fails with validation_failed for some customers

DescriptionAdd a description…

Linked work itemsAdd linked work item

RepoHelpdesk DEV Agent online

You · 12:37 PMS

A customer keeps hitting validation_failed at checkout — bug or config?

grep · read_file traced the code

RepoHelpdesk · 12:38 PM

Why some customers hit validation_failed at checkout

Root cause

Coupon codes are matched case-sensitively. In CheckoutValidator.ts at line 73, any mismatch throws immediately:

if (input.code !== coupon.code) throw new Error('validation_failed');

So SAVE20 is accepted but save20 is rejected. It's configurable — turn on case-insensitive coupon matching under Settings → Checkout.

Ask about this ticket… (Enter to send)

The RepoHelpdesk panel, shown inside a Jira issue.

How it works

Four steps, all inside the ticket — the round trip from question to answer.

Ask in the ticket
A support engineer types a question into the RepoHelpdesk panel on the issue.
The Agent finds the code
RepoHelpdesk hands the question to the Agent paired with the linked project, which searches your repos for the code behind the behavior.
It writes a plain-English answer
The Agent turns what it found into an answer a non-engineer can act on — the cause, and what to do about it.
The answer lands in the ticket
It streams back into the panel with the files and lines it came from, and stays on the issue for whoever picks it up next.

Answers are sourced from the exact commit your Agent has checked out — the code your customers are running right now, not last quarter's wiki.

Install the app

A Jira site admin installs the app once. After that, it appears on every issue for the projects you choose.

Install from the Atlassian Marketplace
Find RepoHelpdesk on the Atlassian Marketplace and install it on your Jira site. You'll need Jira site-admin rights to approve it.
Connect it to RepoHelpdesk
Open Apps → RepoHelpdesk → Connect in Jira and sign in. You must be an admin of the RepoHelpdesk project you're linking — that's what authorizes the connection between your Jira site and your workspace.
Pair a project
In the RepoHelpdesk portal, open the project whose repos back these tickets and copy its pairing token from Settings → Integrations. Paste it into the Jira connection dialog.
Jira → RepoHelpdesk → Connecttoken
```
Project pairing token
rhd_jira_eyJhbGciOiJI••••••••••••
```
Choose which Jira projects show the panel
Pick the Jira projects that should display RepoHelpdesk. The panel appears on every issue in those projects for users who have access.

One Jira project can pair to one RepoHelpdesk project. If your tickets span multiple codebases, pair the project whose repos hold the answers — or use a multi-repo project. See Connect your repos.

Ask about a ticket

Open any issue in a connected project. The RepoHelpdesk panel sits in the issue's activity area. Type a question the way you'd ask a coworker:

"Why doesn't this customer see prices on their deal list?"
"What causes the validation_failed error during checkout?"
"Is the behavior in this ticket a bug, or is it configurable?"

RepoHelpdesk reads the code and answers in plain English. Everyone with access to the issue sees the thread, so the answer becomes shared knowledge instead of a one-off Slack reply. Copy any answer into a comment to share it with the customer-facing reply.

What RepoHelpdesk can see

The integration reads only what it needs to answer, and stores as little as possible. Your code is never part of what we store.

Data	Used to answer	Stored by us
The question text	Yes	Metadata only — sender, time, token count
Issue key & summary	Yes — for context	No content stored
Your source code	Read locally by the Agent	Never
The answer content	Lives on your Agent	Never
Customer data in the issue	Only if you include it in a question	No content stored

The panel doesn't read the full issue automatically — it answers the question you ask. If a question includes customer details from the ticket, that text is sent to the AI model like any other question. Read the full model on the Security architecture page.

Permissions and roles

Who can use the panel follows your RepoHelpdesk access, not just Jira's.

Open by default, with a deny-list. Any project member who connects their Jira account can use the panel. Admins block specific people per integration when they shouldn't have it.
Repo grants carry over. When your project limits who can see which repos, a user only gets answers from repos they're granted. Someone with no access to a repo can't pull answers from it through Jira either.
Admins control the link. Connecting and disconnecting the Jira site, and choosing which Jira projects show the panel, is an admin action in both Jira and RepoHelpdesk.
Every question is in the audit log. Who asked what, when, and which tool calls ran is recorded on every plan — including questions asked from Jira.

Troubleshooting

Most issues come down to the Agent or the pairing. Start here.

Symptom	Likely cause	Fix
Panel shows "Agent offline"	The Agent's connection dropped, or it isn't running.	Run `repohelpdesk-agent status` on your server. See the offline checklist in Install the Agent.
Panel doesn't appear on issues	The Jira project isn't selected, or the app lost its connection.	Re-open Apps → RepoHelpdesk and confirm the project is enabled and still connected.
"Not paired" message	The pairing token expired or was rotated.	Copy a fresh token from Settings → Integrations and re-paste it in Jira.
"You don't have access to this integration"	An admin has blocked your account for this integration.	Ask a project admin to unblock you under Settings → Integrations.
Answers say "I don't have access to that repo"	The asker lacks a repo grant.	Grant the user access to the repo in RepoHelpdesk. See Invite your team.

Still stuck? Email hello@repohelpdesk.com with your project name and the issue key — we'll trace it with you.