Problem Links
See every incident behind a problem ticket in the ticket sidebar, update them all at once, and link tickets to problems without leaving the ticket.
Getting started
- Install Problem Links from the Zendesk Marketplace and choose which agents and groups may use it.
- Open a problem ticket. The Problem Links panel in the apps sidebar lists its incidents.
- Open an incident to see the problem it belongs to, or any other ticket to link it to a problem.
On a problem ticket
The panel shows the number of incidents and, for each one, its status, ticket number, subject, requester, the requester's organization, the assignee and how long ago it was created. Click a number or subject to open that ticket in a new tab of the agent workspace. Large problems load 50 incidents at a time (change this in the settings); Load more fetches the next page.
The status chips filter the list and show how many loaded incidents have each status. While not every page is loaded, the panel says that the counts cover the incidents loaded so far.
Add internal note to all
Write the note (pre-filled from the settings), click Add note, check the number of incidents and confirm. The note is added as an internal note, visible to agents only, never to the requester or other end users. With a status filter active, only incidents with that status get the note. A progress bar follows the run; at the end the panel says how many incidents were updated and lists any that failed, with Zendesk's reason.
Set status on all
Choose Open, Pending, On-hold (offered only when your account has it switched on) or Solved, optionally add an internal note, and confirm. The same filter rule applies, and incidents already in the chosen status are left out. Ticket rules still hold: if your account requires a field before a ticket can be solved, those incidents fail with that reason and the others are updated.
Copy as CSV
Copies the list you are looking at (the loaded incidents in the current filter) to the clipboard as CSV, ready to paste into a spreadsheet or a message: number, subject, status, requester, organization, assignee, created date and a link. It is a copy of what is on screen, not an export of ticket data.
On an incident
The panel shows the linked problem: status, number, subject and how many incidents it has. If the problem was deleted or merged, or you cannot see it, the panel says so with Retry, and Unlink and Change problem still work.
- Open problem opens it in the agent workspace.
- Change problem opens a search box. It lists recently updated problems; type words from the subject, or a ticket number or link, and click Link.
- Unlink removes the link (the ticket stays an incident). Undo in the message puts it back, unless someone has linked the ticket to another problem in the meantime; then the app says so and leaves it.
- Make this ticket a problem changes the ticket's type to Problem after a confirmation; it is then no longer an incident of the old problem.
On any other ticket
Link to a problem searches problem tickets the same way and sets the ticket's type to Incident with that problem. Make this ticket a problem turns it into a problem other tickets can link to.
Settings
| Setting | What it does | Default |
|---|---|---|
| Default internal note | Text the note box starts with. Agents can edit it before sending. | A short "we are working on it" update |
| Confirm bulk actions | Ask for confirmation, with the number of incidents, before a bulk note or status change. | On |
| Incidents per page | How many incidents load at a time, 10 to 100. | 50 |
Permissions and limits
- The app acts as the agent using it, with that agent's Zendesk permissions. An agent who may not edit a ticket gets a plain message instead of a change.
- Closed tickets cannot be changed in Zendesk, so bulk actions skip them and say how many were skipped.
- Before a bulk action the app loads every incident again, so the count you confirm is current.
- Bulk actions use Zendesk's bulk update: 100 tickets per job, at most five jobs at a time (Zendesk allows 30 running jobs per account, shared with your other apps). When Zendesk answers "too many jobs", rate limits or has a server problem, the app waits as Zendesk asks and tries again; it never sends the same job twice.
- If a job could not be started at all, the message names the incidents that were not changed, so you can run the action again for them. Jobs that were started always run to the end in Zendesk.
- If Zendesk is still busy after about two minutes, or you close the ticket while a bulk action runs, the app remembers the jobs in your browser and shows the result the next time you open the problem (Zendesk keeps job results for 24 hours). It does not start a new bulk action on that problem until the earlier one is finished.
- Changes made by the app to the ticket you have open (link, unlink, make a problem) are saved at once, and the app sets the same ticket type in your open ticket so that your next Submit does not undo it. If you have other unsaved edits on that ticket, submit them afterwards as usual. The panel refreshes after your own Submit and when another agent or an integration changes the ticket.
- Problem search shows the ten most recently updated matches and how many there are in total; add words to narrow it down.
- Messages: 403 means your role may not see or change a ticket; 409 means someone changed the same ticket at the same moment; 422 names the ticket rule that blocked the change; 429 means Zendesk is rate limiting, so wait a moment. During a bulk action the progress bar says when Zendesk asked the app to wait and when it tries again.
Frequently asked
Where is the data stored?
Nowhere outside Zendesk. The app runs in the agent's browser and calls only your own Zendesk's API. Aldorock has no server for it and receives no ticket data. See Privacy.
Does solving the problem solve the incidents?
Yes, that is Zendesk's own behaviour when you solve a problem ticket. Problem Links adds the steps Zendesk does not have: a readable list, notes and status changes on all incidents before the problem is solved, and linking from the incident.
Changelog
- 1.0 (November 2026): first release.
