Ticket Resolution in JSM: 5 Ways to Resolve Requests Faster

Ticket resolution is the work between a request coming in and being closed, and most of the delays happen in between: duplicate requests, missing details, and customers asking for updates. The customer portal is where you can prevent most of them. Here are 5 ways to resolve Jira Service Management requests faster, each with the app that supports it.

Handle Incidents in Bulk

How to manage all incidents at once, even when it’s tens of them? If you know about the upcoming crisis, be prepared for future tickets.

Create an auto-merge rule that will merge all tickets about the same bug at their creation. Agents will receive one target issue with the others linked and all data from merged tickets. Description comments can be put into the target issue, and thanks to that, we have all the essential information in one place.

Have all of them at once place, and then answer to all reporters at once thanks to the bulk actions. You can add comments to many issues at once, change statuses, etc., without hundreds of clicks.

Create an announcement banner at the portal with information that you’re already aware of the bug and that your team is working on it. This will stop more people from submitting another ticket.

Thanks to that, you allow agents to focus on ticket resolution instead of answering every reporter. It will speed up meeting SLA. Less copying text, more ticket resolving!

Used extensions

• For Auto-merge rule and bulk actions: Service Pack for Agents
• For Banners: Feature Bundle for Jira Service Management

For the full process, see Jira incident management: 5 steps for handling an outage.

Hack 2: Let Customers Edit Their Requests

Why not put more in customers’ hands? Allow them to edit their tickets! Avoid calls from customers with updates, many threads in comments, and, of course, having agents edit requests. Define conditions, who, and how many times can edit tickets and enjoy the self-service process.

To become a true wiz of self-service, use Assets (Available for Premium / Enterprise Jira Service Management plans) to display products, equipment, and license whatever service you provide to choose. hen, when customers create a request, they can immediately say which product or service it concerns. What’s more! - if there is any mistake, thanks to this solution, customers can edit it too.

Used extensions

• For Edit request: Feature Bundle for Jira Service Management

Read more about how customers can edit requests in JSM.

Hack 3: Collect Customer Data When Onboarding

When you get a new customer, congratulations!, immediately ask for the necessary data for further cooperation, such as region, time zone, language, preferred contact, and anything that makes it easier for future ticket resolution. Display those attributes to fill on the portal and create a sort of onboarding process.

Basic customer information is entered once, immediately upon entering the portal, and is available to the agent without asking for the same information in the comments. Agents can access them from the general view of all customers and the level of a new request created by the customer.

Next time you will get a request, you will thank yourself! No spare questions, one source of truth, no hopping between tools. All data you need right in Jira.

Used extensions

• Perspective | Custom Attributes for Jira

Hack 4: Show the Workflow on the Customer Portal

Communication is the key. But it doesn’t mean asking the same questions all over again or wasting time answering. Provide your customers with all the information they need on the portal. Display the workflow on the request details view and keep your customers constantly up-to-date.

You also display to customers linked issues on the request details view. It makes tracking the status of related tasks easier, even though the customer does not have access to, for example, the software project. Thanks to this, they can see that the task is in progress.

If there is something going on, you plan maintenance, or there is a holiday coming, inform all customers in advance thanks to dynamic banners.

Used extensions

• Feature Bundle for Jira Service Management

See how to show request progress on the JSM customer portal.

Hack 5: Keep Customer Data in Jira

Hopping between tools and creating more and more sheets can be exhausting. Keep customer context in Jira instead, in dedicated Customers and Organizations views.

Agents can adjust columns to their needs and ask clients about additional data on the portal. It is possible to save many views with different customers, for example, dividing them by project, region - whatever you need. This also eliminates questions between technical and sales teams.

It’s getting even smoother with an API that allows getting, creating, and updating customer’s and organization’s data. You can use it to import data once or build a synchronization middleware with other data sources.

This solution also supports Assets so agents can display those that are connected to customers – in the table, issue view, or customer portal Profile view.

Used extensions

Perspective | Custom Attributes for Jira

Resources

Explore other ITSM resources like Whitepaper: Incident communication for service desk agents.

This article was updated on October 26, 2026.