November 16, 2026
Reporting warehouse issues: a service portal instead of a phone chain
By Alexander Kruse, CEO
The handheld scanner at gate 3 stops reading, the label printer at the packing station prints blank labels, and the night shift doesn't know who to call. In logistics, every issue brings part of the operation to a halt.
We show why warehouse issues so often travel by phone and word of mouth, what that costs, and how a service portal with Jira Service Management and Assets turns them into a process that every site uses the same way.
&w=3840&q=75)
How issues often travel today
Without a fixed process, every issue depends on individual people:
Call. The shift lead calls IT, or the colleague who knows about it. If they can be reached.
Describe. Which device, at which gate, since when? Half of it gets lost on the phone.
Pass it on. By email or on a note to whoever can fix it.
Chase. Nobody sees the status, so people call again.
Shift change. The next shift starts from scratch, because the information isn't written down anywhere.
Each step is small. Together they cost hours in which a scanner is missing or a packing station runs slower.
What it costs
The costs rarely show up where they arise:
Throughput: Every minute without a scanner or printer is lost in picking and dispatch.
IT and maintenance are interrupted by calls instead of fixing issues.
Repeat failures: The same device fails again and again, but nobody sees the pattern because there is no history.
Sites each solve the same problem on their own.
A portal instead of a phone chain
Jira Service Management gives every site a service portal. Instead of a blank form there are a few clear request types, such as “Scanner broken”, “Label printer not printing” or “Wi-Fi down in hall 2”. The portal isn't limited to IT: “Roller door stuck” can be a request type that goes to facilities.
The portal opens via a link or a QR code on the packing station or the device. Whoever reports the issue doesn't need to know who is responsible. The report goes to the right team, and the site sees the status at any time without chasing.
Every device has a history
In Assets you map devices, vehicles and sites as objects, and every issue is linked to the affected device. That shows you:
which scanner has failed for the third time this month,
which site has the most printer problems,
which devices are due for replacement.
How to model Assets so they stay maintained is described in Modeling Assets in Jira Service Management .
Around the clock: on-call and SLAs
Logistics runs in shifts, often at night and at weekends too. An issue at two in the morning must not sit in an inbox until the next day. In Jira Service Management you set up on-call schedules, and critical issues alert whoever is on duty. SLAs show whether the agreed times are met, broken down by priority.
We check case by case which of these features are included in your Atlassian plan. How to make SLAs reliable is covered in SLAs in Jira Service Management that your team actually meets .
One process for every site
If every site reports issues differently, nothing can be compared. With a shared portal, the same request types and instructions in Confluence, every site works the same way, and a new site has the process from day one.
Colleagues on site often solve common problems themselves: when they report an issue, the portal suggests matching articles from the knowledge base.
Three questions to start with
Which issues come up most often for you?
Which devices and sites should go into Assets first?
Who needs to be reachable at night, and for which issues?
We work through these questions in a short remote call and sketch your portal from them. Before founding MESKRU, we supported Atlassian environments at logistics companies such as DB Schenker and Imperial Logistics. Today MESKRU is an Atlassian Gold Solution Partner and Service Management Specialized Partner in EMEA.
Read more
The whitepaper Assets in Jira Service Management is free. For everything else we do for logistics companies, from cloud migration to training for sites, see Jira Service Management for logistics .