Ticket Journey: Amazon-style request tracking
In a world of instant updates, a stagnant “In Progress” status on the Jira portal can feel like a black hole. Whether it is an external customer waiting for a shipment or an internal employee tracking a hardware order, silence often leads to frustration and unnecessary “Any updates?” pings. By implementing a Ticket Journey, the Jira customer portal adopts a familiar, Amazon-style progress bar that keeps everyone informed.
The Scenario: Tom’s missing laptop
Tom, a graphic designer, just joined the team and needs a high-spec laptop to start his first project. He submits a request and sees the status move to “In Progress.” Three days later, it’s still “In Progress.”
Tom has no idea if the laptop is being ordered, configured by IT, or stuck in shipping. Without a visual breakdown, Tom starts emailing the help desk. With a Ticket Journey, Tom could see exactly where he is in the process—from “Order Placed” to “IT Configuration” and “Out for Delivery”—without ever leaving the self service customer portal.
How to set it up: 5 simple steps
Transforming the customer portal experience into a transparent timeline is straightforward with Feature Bundle:
Map the workflow: Define the specific stages of the “Laptop Order” within Jira Service Management.
Access Ticket journey: Navigate to the app settings and select the relevant request type.
Build the stages: Create individual steps (e.g., Procurement, Setup, Shipping) and assign a JQL condition to each so the bar moves automatically.
Add context: Write brief descriptions for each stage so Tom knows what “IT Configuration” actually entails.
Match the brand: Customize the colors and layout (horizontal or vertical) to ensure the timeline looks native to the Jira portal.
Why it’s a game-changer
Proactive transparency:
Users like Tom are always in the loop. They know what is happening now and what comes next, which builds massive trust in the support process.
Agent efficiency:
When the Jira customer portal answers the “Where is my stuff?” question automatically, agents can focus on technical tasks instead of answering status inquiries.
Crystal clear touchpoints:
Every status becomes a meaningful milestone. This clarity is essential for effective incident management in Jira.
Self-service growth:
Visualizing the process encourages a “self-service first” mindset, as users rely on the portal for information rather than manual follow-ups.
Looking for a deeper dive?
The ITSM Handbook serves as a complete guide, packed with strategies for building a world-class customer portal and perfecting incident management in Jira.