A JSM agent’s playbook for solving tickets faster with historical context

[#1]

History repeats itself—especially in customer support. We’ve all been there: an agent spends 30 minutes troubleshooting a complex issue, only to realize later that the customer had the exact same problem last month, or worse, has already opened a duplicate ticket that another agent is currently working on. Without immediate visibility into a customer's history, agents waste time, provide inconsistent answers, and miss the "big picture" of a customer's journey.

Who this is for

• Primary Audience: JSM Agents, Support Managers, and Jira Admins.

• Environment: Jira Cloud.

• Marketplace Link: Related Tickets For Jira Service Management Cloud

---

Native Jira approach (and limitations)

In standard Jira Service Management, an agent looking for context usually has to:

1. Manual Search: Run a JQL query for the reporter’s name or email.

2. Tab Hopping: Open multiple browser tabs to compare previous tickets with the current one.

3. Memory Reliance: Hope they remember seeing a similar summary earlier in the day.

The limitations: This process is manual, prone to human error, and adds significant "context-switching" overhead.
When the queue is moving fast, agents often skip these steps, leading to duplicate work and a fragmented customer experience.

Solution walkthrough: Automating context with Related Tickets

By using Related Tickets for Jira, you can embed a historical view directly into the issue panel. This ensures that every time an agent opens a ticket, the context finds them.

Step 1: Install and Register

Once installed, the app provides a dedicated panel in the Jira issue view of the Service Management project. 

Step 2: Instant Duplicate Detection

When a new ticket arrives, the agent can immediately see if the same reporter has any other tickets.

Caption: The app automatically surfaces the reporter's recent history so agents don't have to search manually.

---

Proof / Example: The "Before and After"

Scenario: A software company receives a "System Down" alert from a VIP customer.

• Before: Agent A starts investigating. Ten minutes later, Agent B starts investigating a separate ticket from the same customer. They both spend 20 minutes on the same logs before realizing they are duplicating effort. Total time wasted: 40 minutes.

• After (with Related Tickets): Agent A opens the ticket and immediately sees a "Related Ticket" opened 2 minutes ago by the same user. Agent A leaves a comment on the second ticket, links them, and handles both simultaneously. Total time saved: 20 minutes + 1 very impressed customer.

Ready to give your agents the context they need to shine?
Install the free app today. Related Tickets For Jira Service Management Cloud