Connectors

/

Zendesk

/

Link a Zendesk ticket to a Jira issue
Write
Cross-Connector

Link Zendesk tickets to existing Jira issues both ways

For support teams who want a ticket and a known Jira bug pointing at each other, without duplicate links, by asking their AI assistant.

Try PopdockAI free
Get a live demo
Link a Zendesk ticket to a Jira issue
Link Zendesk ticket 51204 to Jira issue PAY-317.
Ticket 51204 and PAY-317 are not linked yet. - Ticket: Invoice export times out, Contoso, high priority - Issue: PAY-317, Invoice export times out on large accounts, In Progress - Changes: an internal note on the ticket, a comment on the issue, and a link back to the ticket Shall I link them?
Zendesk
Sample figures. Your results come from your own account.
zendesk-get-ticket
jira-get-issue
zendesk-get-ticket-comment
jira-add-issue-comment
jira-add-issue-remote-link
jira-get-issue-watcher

On this page

The problem

The problem

The prompt

Who it's for

How it works

Tools used

Connector

Zendesk

Zendesk
Run it on your own Zendesk data.

Connect Zendesk, pick your AI tool and paste the prompt.

Try PopdockAI free

The problem

Ticket and bug links end up one way or doubled

When a ticket is about a bug engineering already tracks, the two records should point at each other. Linking by hand means notes in two systems, and the same pair gets linked twice or only on one side.

Without PopdockAI

  • Check the ticket notes for an earlier link
  • Add an internal note on the ticket
  • Comment on the Jira issue with ticket details
  • Leave a one way link when one step is missed

With PopdockAI

  • Both records are confirmed to exist
  • It stops if they are already linked
  • You compare subject and summary before anything is written
  • A half made link is reported so only that part is retried

The prompt

Use this prompt

Copy it into any AI tool connected to PopdockAI. Swap the values in braces for your own.

Prompt
**Objective:** Link Zendesk ticket {ticket-id} to the existing Jira issue {issue-key} so both records point at each other.

**Step 1: Confirm both records exist**

Call `zendesk-get-ticket` with ticket-id {ticket-id} and `jira-get-issue` with issue-key {issue-key}. If either is missing, report which and stop.

**Step 2: Check for an existing link**

Call `zendesk-get-ticket-comment` with ticket-id {ticket-id} and public false. If a note starts `Linked Jira issue: {issue-key}`, report that they are already linked and stop.

**Step 3: Confirm, then write**

Show the user the ticket subject and the issue summary side by side and wait for confirmation. Then:

1. Call `zendesk-add-ticket-comment` with ticket-id {ticket-id}, public false, and a body whose first line is `Linked Jira issue: {issue-key}`, followed by the issue summary and status.
2. Call `jira-add-issue-comment` on {issue-key} with the Zendesk ticket id, subject, requester organization and priority.
3. If {zendesk-subdomain} is not empty, call `jira-add-issue-remote-link` with url https://{zendesk-subdomain}.zendesk.com/agent/tickets/{ticket-id}, title Zendesk ticket {ticket-id}, application-name Zendesk and global-id zendesk-ticket-{ticket-id}.

**Step 4: Report**

Which writes succeeded, and that this issue will be found from the ticket but not from Jira-side searches by `[ZD-{ticket-id}]`, because its summary was not changed.

**Rules & Guidelines:**

* `zendesk-get-ticket`, `zendesk-get-ticket-comment` and `zendesk-add-ticket-comment` are on the zendesk server. `jira-get-issue`, `jira-add-issue-comment`, `jira-add-issue-remote-link` and `jira-get-issue-watcher` are on the jira server.
* Do not rename the Jira issue with `jira-update-issue` and do not call `zendesk-update-ticket`. The Zendesk note must have public false.
* Linking convention used by every prompt on this server: an escalated Jira issue's summary starts with `[ZD-<ticket id>]`, and the Zendesk ticket carries an internal note whose first line is `Linked Jira issue: <ISSUE-KEY>`. Find links by either marker.
* Jira issue ids: `jira-get-issue` returns the issue key but not the numeric id. Pass the key (e.g. ABC-123) where a Jira tool asks for an issue id; Jira accepts either. If Jira rejects the key, call `jira-get-issue-watcher` filtered by issue-key and take its issue-id.

**Validation:**

* If the Zendesk note succeeds and the Jira comment fails, report the half-made link so the user can retry only the Jira side.

Who it's for

One answer, three teams that use it

Support agents

Attach a ticket to a known bug

Link a customer ticket to the Jira issue already tracking the bug, so you can tell the customer when it is fixed.

Connect Zendesk ticket 50566 to the existing Jira bug WEB-904.

Developers

See which customers a bug affects

Each linked ticket appears as a comment on the issue with its details, so you know who is waiting on the fix.

Add Zendesk ticket 49905 to Jira issue APP-212 so engineering can see the customer report.

Support escalation leads

Stop duplicate and one way links

Existing links are checked first and partial failures are reported, so every pair is linked once on both sides.

Is Zendesk ticket 51788 already linked to CORE-77 in Jira? If not, link them.

How it works

What PopdockAI does when you ask

You give the ticket and the issue, and your AI assistant checks for an existing link first. Nothing is written until you confirm, and nothing public is posted.

01

Ask

You give the Zendesk ticket and the Jira issue.

Your AI tool

02

Check

It confirms both exist and stops if they are already linked.

zendesk-get-ticket
zendesk-get-ticket-comment
jira-get-issue

03

Confirm

You see the ticket subject and issue summary side by side.

No items found.

04

Link

It adds an internal note, a Jira comment and a link back where possible.

Your AI tool

What PopdockAI provides

The tools behind the answer

Ready made tools for Zendesk and one secure connection to your AI tool. No code, no exports.

get-data

zendesk-get-ticket

Returns Zendesk support tickets with their status, priority, requester, assignee, group and organization. Filter by status, priority, assignee, group or dates to find the tickets you need.
get-data

jira-get-issue

Returns Jira issues with their project, issue type, status, assignee, reporter, dates and estimates. Filter by project, status, assignee or date range to pull a backlog, a sprint or one person's open work.
get-data

zendesk-get-ticket-comment

Returns the comments on a Zendesk ticket, both public replies and internal notes, with their author and when they were posted.
run-action

jira-add-issue-comment

Adds a comment to a Jira issue, which is the usual way to record why something was reprioritised, reassigned or closed.
run-action

jira-add-issue-remote-link

Links a Jira issue to a page or record in another system, with a title and a URL. Issue linking must be enabled in Jira.
get-data

jira-get-issue-watcher

Returns the users watching Jira issues, with the issue and project they are watching, so you can see who is following a piece of work.
Read only.Nothing in Zendesk Changes

This report is built from Get data tools only. PopdockAI applies the row, field and parameter rules your admin sets, and every query is written to the audit trail.

How Popdock AI secures your data

The outcome

One problem, traceable from either side

Try PopdockAI free
Get a live demo

Related use cases

More ways to put this data to work

All Ramp use cases

One prompt template with infinite possibilities.

‍

Your AI assistant adapts its approach, tone, and capabilities to match each unique context while you maintain a single, manageable workflow.

Join forward-thinking companies that are transforming their operations with intelligent, secure AI automation.

Try PopdockAI Free
See Documentation