Link the Machine to Its Jira Ticket: One Scan Is All It Takes
The Issue URL Barcode field turns any Jira issue into a printable, scannable label that opens straight back to that issue. Choose barcode or QR, print it, scan to open.
You’re standing in front of a machine on the factory floor and you need its service history. It’s in Jira, and nothing on the machine tells you which issue to open. So you walk back to your desk, search by asset tag or by memory, find the right issue, and write up what you saw ten minutes after you saw it.
The Barcode/QR Custom Field for Jira has a field type for exactly this: Issue URL Barcode. Add it to an issue type, and Jira renders that issue’s own URL as a barcode or a QR code. Print it, stick it on the equipment, and a phone camera gets you back into the ticket.
What gets encoded
The field takes the issue’s key and your instance’s base URL, builds a link like https://yoursite.atlassian.net/browse/ECP-104 the moment it renders, and draws that link as either a Code128 barcode or a QR code. You can’t type in something else, so a label can’t go stale or end up on the wrong ticket six months later.
If the label needs to carry a serial number or an existing SKU instead, that’s the Editable Barcode field in the same app, which we’ll cover in an upcoming post in this series.
Configuring the field: barcode or QR code
When you add the Issue URL Barcode field to an issue type, the configuration screen gives you two choices: whether the link is drawn as a Code128 barcode or a QR code, and where the code sits on the issue, left, center, or right.
QR is the safer default. A phone camera picks it up at an angle, in bad light, from a bit of distance. Code128’s advantage is its shape: a long thin strip fits a narrow tag or a shelf edge where a square won’t.
Worth checking before you commit to one, though: plenty of handheld scanners still in service read 1D barcodes only. If the people scanning won’t be using their phones, the hardware may decide this for you.
What shows up on the issue
Every issue of that type renders its own code right on the issue view, with no extra step from whoever opens the ticket. The encoded link is printed just beneath the code, so you can read it off the screen and check that it matches the issue you have open. Next to it is a small download button for printing.
Printing a label that actually holds up on a shop floor
The download button opens a print dialog. You choose a size, in pixels, millimeters, centimeters, inches, or points, and a paper size from A5 up to A0, and the app builds a PDF at those dimensions, with the encoded text printed underneath the code and the file automatically named after the issue key, so ECP-104-barcode.pdf never gets confused with a different ticket sitting in the same downloads folder.
Where this is useful
A few situations where it fits:
- Physical assets with a Jira history: a machine, tool, server, or unit of stock that already has an issue tracking its work.
- Maintenance and inspections: whoever’s in front of the equipment opens its exact ticket with a scan, instead of walking back to a terminal to search for it. This is where the time actually goes.
- Reused, long-lived issues: printed once, correct for years.
- Warehouse and inventory shelves: a scan on the shelf edge opens the exact issue.
- People who don’t spend their day in Jira: they recognize the equipment on sight but have no idea what its issue key is.
The Barcode/QR Custom Field is on the Atlassian Marketplace, if you want to try it on your own Jira issues.