Appearance

Issue Links ​

Issue links connect a support ticket to the engineering issue that will fix it. Technicians and the agent can see which tickets wait on which issue, developers see how many tickets an issue affects, and when the issue closes the agent drafts the update for the requester.

Prerequisites ​

Linking a Ticket to an Issue ​

  1. Open the ticket and find the Linked issues section in the details drawer.
  2. Click Link issue.
  3. Paste a GitHub issue URL or owner/repo#number, or a Linear identifier such as ENG-123, and click Link.

Each linked issue shows its state (Open, Closed, or Not planned), the pull requests that closed it, a link to open it in GitHub or Linear, and an unlink control. Many tickets can link to the same issue. Pull requests cannot be linked directly.

Issues the agent creates in GitHub from a ticket's chat are linked automatically.

What the Agent Can Do ​

In Explore and ticket chat, the agent can list a ticket's linked issues, link or unlink an issue, and post a comment on a linked issue. Comments are a summary written for developers; the requester's own message and personal details are never copied across. These actions run without an approval prompt.

What Developers See ​

On a linked GitHub issue, Junto maintains a single comment that it edits in place, such as "Linked Junto tickets: 3 (2 open)". On private repositories the comment lists each company and ticket number; on public repositories it shows counts only. Requester replies are never mirrored to GitHub. Linear issues do not receive this comment.

When the Issue Closes ​

When a linked issue is closed, every open linked ticket gets an approval card in its chat, titled along the lines of "Tell Jordan the fix shipped: acme/tools#45" (or "closed as not planned"). The card carries a customer update drafted from that ticket's own conversation.

  • Approve & Send posts the update to the requester as a customer-visible note through your PSA.
  • Dismiss removes the card, with an optional reason.

The draft is sent as-is or dismissed; it cannot be edited on the card. If the issue is reopened, any unanswered card is withdrawn. Tickets that are already closed receive no card.

GitHub closures arrive within seconds. Linear closures, and any GitHub events that were missed, are picked up by a check that runs about every 15 minutes.