According to CCW Digital, customer experience and customer service management are the priority for over 50% of organizations. Obviously, it’s important to pay attention to both these aspects because otherwise, when the clients encounter problems during the process, they become frustrated, lose trust to us, and turn to our competition. This means enabling customers to have easy access to all information, as well as smoothly go through every touch point of customer journey in the support process. We should do all in our power to create user-friendly support experience, especially on such a complex channel as Jira Service Desk. We’ve already set up and customized the Help Center, Request Form, and Request Detail View screens clearer, understandable, and more involving. Now, let’s take care of My Requests list and make it more informative than what the default configuration offers us.
My Requests – all requests in one place
Default My Requests list in Jira Service Desk Server
In general, we belong to more than one Service Desk on the specific Help Center. That can be problematic for the customers when they raise many requests on various Customer Portals. That’s what My Requests screen is for – it gives the users the possibility to view the list of all the requests they created or participate in on a given instance. Here, the clients can not only see their requests with basic information such as reference number, service desk or status, but also do some simple actions such as filter them by their status, creator or request type, and search the requests.
Why default My Requests isn’t enough?
These basic functionalities mentioned above are very limited. There’s no possibility to set which fields we want to see as columns nor sort the requests in these columns. When filtering by Status, the clients can only choose between Open and Closed. The search works only for issues’ Summaries, which in most cases makes it unusable. Also, Jira Service Desk doesn’t give us any possibility to customize this screen natively, as well as there are no workarounds like scripts.
For example, the customer has no information about the assignee or how long does he has to wait for his request to be solved, because there’s no such column displayed on his My Requests list. Or, when an agent asks the client about which one of his issues with Highest priority is the most important for him. When customer looks at his list with requests there’s no Priority column there he could sort or filter by. That’s when the problem arises, especially when it’s a customer with more than 100 requests on his list. How can he tell which ones have the Highest priority other than browsing through all the requests and making a separate list of them in his notebook? And, he needs to do it only to choose the one that’s the most urgent for him.
Instead of relying on default settings of My Requests list, we should check our options because we sure will find some on Atlassian Marketplace.
Advanced customization with Atlassian Marketplace apps
My Requests Extension for Service Desk is one of a few apps dedicated solely to My Requests list. As admins, we choose which fields they can add as columns, and which of them will be displayed by default, as well as we can globally limit the fields’ visibility for selected user groups. For example, we can enable such columns as Assignee, Priority or Budget for the customers only from VIP user group, thus giving them the possibility to add these fields as columns to their list. This way, we protect such confidential information as budget from users who aren’t authorized.
Also, the customers don’t have to worry about keeping it all in the right order from the beginning. They can drag and drop each item as they see fit. However, as the app is version 1.2 at the moment, not every field is available to choose from. Basically, for now every custom field and most system fields can be used as columns, including those which most customers ask for: Priority, Assignee, Due Date, Created, Updated and Resolved dates, among others. In the future, My Requests Extension will also support FixVersion/-s and AffectedVersion/-s fields. In other words, the app enables us to display all the fields we can display on Request Detail View, even those which can be added there with Extension for Jira Service Desk.
Adding columns to the request list and ordering them
Other than that, My Requests Extension enables users to customize the requests list to their needs. Also, it offers advanced filters like filtering the requests by exact Status and choose a specific Service Desk where we raised our requests. We’re going to increase the number of available filter options in the next releases as well. Other than that, we can sort each column other than Customer Request Type and Organizations alphabetically, and define how many requests will be displayed on one page.
The searcher provided by the app is also extended and enables searching through Description fields as well. You can also make use of special characters – for example, to exclude expressions from the search results.
As a result of this simple setup, My Requests list becomes clear and personalized, allowing to display more information and securing some fields at the same time. However, this app is in its first versions, but we’re already working on version 2.0 of the app which will include possibility to save user’s configuration and create separate queues for each filter, i.e. separate lists with Waiting for support or In Progress requests. Also, anytime now, we’ll add the option to export the lists to .csv. For now, feel free to test My Requests Extension 1.2. and leave your feedback! It will help us greatly to improve and adjust the app to your needs.
This is the fourth part in the series of articles about improving customer experience with Jira Service Desk Server. Watch this video for more details on customizing the My Requests List.
If you’d like to learn more about My Requests Extension for Service Desk, take a free 30-day trial from the Atlassian Marketplace. You can also book a live demo via Calendly, if you’d like to see the app in action.